More importantly, though, I love that you read 2 paragraphs and then blew your top ("what a load of crap" -- really?) over a parenthetical comment that was already qualified with a "probably."
From an acclaimed Apple-enthusiast: http://daringfireball.net/2004/10/themes
Ever seen the window controls for a full-screen iTunes 10? http://zapp0.staticworld.net/reviews/graphics/products/uploa...
More: http://watchingapple.com/2008/05/how-apples-contextual-menus...
May Jobs rest in peace, but iOS 5 didn't just materialize in a single day, and Jobs presented it, undoubtedly as the next-best sliced bread, at WWDC.
More importantly, though, I love that you read 1 paragraph and then blew your top ("belligerent" -- really?) over a comment. It's really tiring to hear about how "if only Jobs were here" or "Jobs would never let this happen!" pg should know better, and so, I won't hold his hand.
Pg said that forcing consistency tends to result in bad design decisions. Maybe jobs could do it, page can't.
To disprove that point, you'd need to show an example of forced consistency across apple platforms that degraded usability. Showing inconsistency isn't responding to the argument.
I really didn't want to compare Apple and Google or Page and Jobs; that's the point. We're not even comparing the same things, and you don't have to look far to find power users scorning The Apple Way. We can go on all day with issues pertaining to Apple's HIG -- forced consistency -- and the degrading of usability.
1. Pg says forced ui consistency tends to be bad. 2. Maaaybe a skilled design genius like jobs could do it (maybe), but most people shouldn't try.
His argument didn't turn on Jobs. It was a rhetorical flourish to bolster the idea. If even the best in the field (according to pg) couldn't do it well, then others should be wary.
The top-most comment is fair to point out bugs, but I don't see the correlation with Jobs and his genius, UI/UX brush. Are you suggesting mandates for consistent UI -- whatever that has to do with the article's discussion about the compose window -- creates more bugs? Makes Maps slow? They should fix those things, but it has nothing to do with UI / UX consistency nor Jobs.
How do you know what anything does with graphical-only buttons, in Gmail compose UI, Android copy/paste UI, etc., without tapping everything at least once and potentially losing data?
As for Android, sure there is no undo, and I wasn't really speaking for Android, but I'd, again, be really surprised if the cut/copy/paste is statistically confusing. I'd only suggest the paste option only be offered in the context-menu above the selection and not also next to the cut/copy icons. I'd also argue that it's really unlikely I'd be doing anything with an Android device that isn't repeatable with little effort or would be undoable and before I possibly had to cut my teeth once or twice. I think iOS did a better job here, as Android offers no means of backing out a change.
[0] http://www.tuaw.com/2011/12/06/on-ui-inconsistency-in-ios-5/