3 ms·

I don't really like this kind of inflammatory article. It usually starts from the premise "My UX preferences are universal and whatever tradeoffs the developers

I don't really like this kind of inflammatory article. It usually starts from the premise "My UX preferences are universal and whatever tradeoffs the developers are trying to optimize are irrelevant because they should focus on X Y and Z instead", and expands from there. I used to re-enable the menu bar in Firefox and Atom all the time, until I realized I never used 95% of it and the remaining 5% could be accessed from elsewhere, saving me some vertical space. I don't like having a menu bar on top. I prefer the Windows-style UX with all the OS widgets and windows list tucked in a bottom bar. (I tolerate the top bar in Pop Shell because its great tile management means I don't need to use the mouse too much for navigating). I do agree with the author's point about discoverability, though. There's a lot of room to improve there.

PoignardAzur 5y ago
To give another example (from part 3): > Why on earth would I ever want to switch to a “wrong” (that is, non-matching) keyboard language? Mac OS X had this, in my opinion, counter-productive menu Because sometimes I play video games and sometimes these games have hardcoded keybindings that assume I have a QWERTY keyboard, and if I want to be able to play the game at all I need to play along. Now, sure, there's room for improvement. Maybe we don't need a keyboard shortcut to change the language mode, as long as there's a top-level menu that gives me a way to do that. But a UX designed by the author wouldn't give me either of those options. Because the author never met that use-case, and therefore assumed the use-case didn't exist.