3 ms·
Please, stop talking about eye candy if you don't have a deep understanding of UI design. The most important aspects of UI are about presenting information in
by hyperpape 14y ago
Please, stop talking about eye candy if you don't have a deep understanding of UI design.
The most important aspects of UI are about presenting information in a way that is comprehensible. Flashing error messages on screen for less than a second is confusing--either the information is important and needs to be visible for longer, or it should be relegated to a log file somewhere.
Upthread, someone said that showing all the output of the init scripts in a tty feels cheap. I agree that it feels cheap--and it feels cheap because it suggest something about the computer. Older OSes spent a lot of time displaying initialization script outputs to the screen because that you had to know about it. At any time, that shit might be broken, and you (or your sysadmin) would have to reconfigure it. That's the wrong message to send to your average Ubuntu user.
So if you thought that complaint or many of the complaints from the initial article were about "eye candy" you were wrong.
- qb45 14y agoI still believe that resources would be better spent on fixing stuff rather than "sending a message" that it isn't broken. And BTW, I'm a big fan of printing output of init scripts to console, provided that it's nice and concise (as it used to be in most distros few years ago) because it greatly aids debugging when (not if) stuff breaks. It's one of the reasons I left Windows, actually.
- hyperpape 14y agoI enabled it on my old Mac--because I am a huge freaking nerd. I never once needed it, but it made me happy. However, I think it's definitely a bad default. Make it easy to enable, and the people who need it will enable it. But we should design and build for the normal case first.