News for hackers. Stuff that matters.
Re:The Rule of Silence (2006) by pwdisswordfish on Tuesday December 13, 2016 @06:54AM (#13166140)
The text-oriented nature of Unix may be a mistake, but the Rule of Silence is not concerned with it. It is about not overwhelming the user with information they are not interested in. GUIs can follow or violate the Rule of Silence just as well.
Re:The Rule of Silence (2006) by StRoy on Tuesday December 13, 2016 @11:06AM (#13167782)
Talking about the rule of silence in GUIs, I wish I could slap the eurocrats who decided to force websites to show the cookie warning on a first visit of all websites. Did they even understand the consequence and wasted time of what they were doing? Having to click all the time to get this dumb warning off?

Of course some websites had to do it in an even dumber way than the law asks for. Like slashdot: http://i.imgur.com/5Fp0nmo.png

This is what greets the French every time slashdot decides to forget you agreed to let them put cookies on your computer and you need to click continue before you can get to the actual website.

The law actually made it worse for the people it's supposed to protect (those who might refuse cookies for privacy?) because those warning then will stick around like glue if they can't give you a cookie to remember you accepted their existence.

Re:The Rule of Silence (2006) by pwdisswordfish on Tuesday December 13, 2016 @11:17AM (#13167891)
The 'best' part is that the only way to remember the fact that the warning was shown (and not display it any more) is to use a cookie or something functionally equivalent to one.[0] So instead of empowering people who wish to protect their privacy, these warnings push people even further to keep cookies enabled.

[0] Storing it server-side, per IP address, is obviously impractical.

Re:The Rule of Silence (2006) by restalis on Tuesday December 13, 2016 @09:22AM (#13166934)
"GUIs can follow or violate the Rule of Silence just as well."

It would have been nice if this was permitted to be violated only by GUIs. Ask about the first-time *nix experiences before the GUI-embracing era and one of the few things they were noticing was the continuous text-spitting. For instance, that was happening on boot and OS loading sequence (and still happens, now only being hidden by default with splash-screens), a lot of reporting about all the things that were performed successfully. It's funny in this regard seeing Unix' Rule of Silence being respected more... outside Unix, where is just common sense, with no need to be formulated as rule.

Re:The Rule of Silence (2006) by pwdisswordfish on Tuesday December 13, 2016 @11:01AM (#13167740)
Booting up is a bit of a special case that I'd actually be willing to carve out an exception for. When the boot-up goes wrong, it's often due to causes so deep that they leave you with very few means of diagnosing it or showing an error message. If the booting process hangs, having a rough idea at what stage it happened can be very helpful. Without these messages, discovering the cause of failure would be much harder.

The boot-up splash screen hardly even counts as "GUI" anyway.

Re:The Rule of Silence (2006) by SixSigma on Tuesday December 13, 2016 @07:50AM (#13166392)
Your comment was saved. Click OK to continue.
Re:The Rule of Silence (2006) by kulu2002 on Tuesday December 13, 2016 @09:02AM (#13166779)
Precisely!