@sjolsen not really, cuz if @tantacrul evidenced one thing, it's that #UI & #UX can be quantified as "good" and/or "bad" and actually implement the best possible option given the workflows at hand (conversely to what @landley once said: #FLOSS can do UI & UX; [tho he also said that consistency is key and #Tantacrul certainly does not just design but also tests this designs more thoroughly than most GAFAMs do their products...])

• And I do have to give him credit for modernizing applications that indeed need some overhaul, as #Audacity did look like something from #Windows95, #macOS9 or #Amiga (and we all can agree that any application from back then that's still around regardless if #Photoshop, #Cubase or even #Sibelius had to move on and change…).

Personally I do hate the #RibbonUI because it's wasteful in terms of screen space and demands way more clicks and mouse travel in my workflows.

• So the #Ribbon clearly works better on #HiDPI, #HighResolution Desktops and #Tablets, not on a *"#LowDPI, #LowRes Keyboard and Trackpoint system…

@n_to @benni @lizzard entgegen anderslautender Meinung kann sowas wie #UI & #UX quantifiziert und qualitativ bemessen werden.

• #Ribbon-Menüs sind shice weil mehr Mausweg.
• "#VibeCoding" ist gequirtle shice!

https://infosec.space/@kkarhan/115213955914130954

@elfin @tantacrul And no @fuchsiii , I don't consider that #Ribbon #UI because by that metric the menu bars in #MicrosoftOffice 4.2 - 2003 were also #RibbonUI!

https://oxytodon.com/@fuchsiii/115147927319883247