Rules From a User to Software Developers
brooksreview.net
brooksreview.net
Funny to read this example since Twitter used to be named "Twttr"! I guess they understood the problem soon enough!
Digg works because Snoop Dogg paved the way.
Kind of like saying "don't design a laptop uglier than a Macbook." Sure, you can do it, but you may be optimizing the wrong thing (and/or at the wrong time).
This is why I don't use Chrome (browser or otherwise), FF 4.0, IE 9, or any of the legions of applications that ignore the basics of functional UI design.
For the vast majority of us, the computer is a tool, not a toy. I have work to do, so trying to figure out where you've hidden key features of your application is something I haven't the time or the patience for.
If it doesn't have a menu bar I won't waste time with it.
After getting used to it (another five seconds) I now prefer it to the standard system of using >1cm of space for something I rarely use in a web browser.
No good can ever come out of change. If things aren't the way I recognize them and like them, then they are obviously inferior because as we all know, functional UI design never changes. The principles that we had when Windows XP came out should still be in use because that's what I'm familiar with.
And I completely agree with you about using the a computer as a tool not a toy. If I can't immediately change the tool in a way that is familiar to me, it is worthless to me. For instance, the first thing I do when I get a hammer is take it apart and see what kind of different colors I can make the handle. That's how I know it's a good and usable tool. And I've found that the most customizable tools are usually the most usable tools. If I can't choose the font face used on my screwdrivers, I don't even bother.
I think we got two different things out of the article. It seems like you got the impression that it was saying that changing things shouldn't happen. I got the point that change for the sake of change is stupid. But if you identify behaviors that people do and don't do, and you change your product accordingly (like Chrome has done) then it's probably a good case for change.