More of an old-man-yells-at-cloud rant than anything actionable here. I agree with the broad strokes, in particular the UX trend towards making everything as fl

More of an old-man-yells-at-cloud rant than anything actionable here. I agree with the broad strokes, in particular the UX trend towards making everything as flat and monochrome and sparse as possible. I really get the impression that "modern" UX designers won't actually be happy until their app is functionally reduced to a big white fullscreen borderless rectangle with a three gray words in the middle that you have to mouse over before you discover they are actually clickable. I disagree with this part of the article, though: > We need to bring back the Ok and Cancel buttons. Historically, OK and Cancel was mainly a Windows UI custom, and the problem with them is that they often leave a lot of room for ambiguity. I see some variation of this at least once a week, you tell me what happens here, I'll wait: > Are you sure you want to cancel the upgrade? This may result in an unbootable system. > (Cancel) (OK) There are multiple other problems with OK/Cancel which I don't have the energy to get into, but the highlights are: 1. Who decided that OK/Cancel made better answers to boolean questions than simply Yes/No? 2. Buttons like this should _always_ be verbs for very short phrases that describe what you are doing when you click on the button. That way, the user is much more sure of what they are doing, and the programmer does not have to write (as) complicated questions. This has been a standard UX concept for decades that is still frequently ignored. 3. I have seen multiple websites/apps where OK/Cancel buttons are swapped arbitrarily. Sometimes OK is on the left, sometimes OK is on the right. This how programmers can gaslight their users.