Yeah, I guess I was overstating the case for rhetorical purposes. I don't think there's never a UI change that improves on what you already know. Once in a while a new interface comes along that's so much more efficient that it's worth retraining yourself. What I'm trying to say is that these changes are rare. I think designers tend to overestimate the benefit of a change and underestimate the power of habituation.
(P.S. thanks for catching my typo ("haver"). Fixed it.)
"In a web browser, sure, the UI barely matters."??? In a web browser, the UI is the ONLY thing that matters. Every browser out there can render a web page. It's how it responds to the user and what it enables you to do that makes all the difference.
The biggest reason I stick with FF is the pentadactyl extension - A browser without decent vi-like controls is intolerable to me, and chrome's equivalent isn't up to par. So I stick with FF, for the UI.
This just isn't true. In a web browser, sure, the UI barely matters. Going through the menus in Firefox or Chrome is rare, enough so that Chrome tends to look different every time I do it.
But for real programs, the UI defines the workflow, and that should be optimized, even at the expense of familiarity. Just be sure that it actually IS better.
So yes, the quoted advice should probably be considered and possibly adopted by FireFox and maybe Chrome. But desktop software shouldn't accept it without a huge dose of salt.