Domain: bikeshed.com
Stories and comments across the archive that link to bikeshed.com.
Comments · 9
-
Re:"bikesheding"???
-
Re:Comments on the browser itself?
For example, have they finally reverted "tabs on top"?
You're a prime example of why Mozilla doesn't take any of this recent huff seriously. Your concerns are meaningless, negligible, and amount to nothing but white noise. You are bike-shedding in your own world. You act as though there isn't even a clearly and readily available GUI option to disable Tabs On Top.
It'll be nice in a few more months when everyone has naturally gotten over their all-too-human completely irrational emotional response to change. Mozilla shouldn't fall for any of this bullshit in the meantime.
-
Re:Does Mozilla not read Slashdot?
Mozilla probably understands how extremely insane people get when they encounter even the most minute form of change (e.g. how often an arbitrary version number is incremented), let alone some of the more major and necessary overhauls they've been attempting. They have real work to do instead of participating in bike-shedding on Slashdot all day.
-
Re:User Interface Design
Why Should I Care What Color the Bikeshed Is?
The best part: "Some people have commented that the amount of noise generated by a change is inversely proportional to the complexity of the change."
-
Re:What's that old saw?
when it comes to complex, interesting questions of language design, very few people are even vaguely qualified to comment, and when it comes to issues of whitespace every idiot on the planet has an opinion
Ahhh! The old bikeshed metaphor! I've been using this one a lot as a web developer...
Some people have commented that the amount of noise generated by a change is inversely proportional to the complexity of the change.
-
Re:Simply put
Another good example for similar behaviour is the Bikeshed: http://bikeshed.com/
-
Bike shed painting.
I would not have thought that machine names could arouse such a passion.
Why Should I Care What Color the Bikeshed Is?
From http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/misc.html#BIKESHED-PAINTING:
"The really, really short answer is that you should not. The somewhat longer answer is that just because you are capable of building a bikeshed does not mean you should stop others from building one just because you do not like the color they plan to paint it. This is a metaphor indicating that you need not argue about every little feature just because you know enough to do so. Some people have commented that the amount of noise generated by a change is inversely proportional to the complexity of the change." -
Bike shed?I mean they literally got into an argument over whether or not the resizing of that box was allowed. It's actually much easier to spark a big argument over something trivial than something complex. See the bike shed story, which better read in full than any summary I can make. (Pst, if you don't like the colors, turn on javascript and refresh.
:) ) -
Re:Firm LeadershipIt's the bikeshed problem: everybody agrees that we want a bikeshed, and that it needs to be painted to keep from rotting, and nobody has a particular color it has to be, but nobody feels empowered to go out and buy paint, in case somebody turns out to be deeply offended by the color choice. That's not the bikeshed problem at all. The bikeshed problem is when you've proposed a major new construction with the latest high-tech infrastructure, and while the construction company was at it, you had them build a bike shed out back for the forward-thinking commuters; when you put the proposal in front of the board, they nod approvingly at the high-tech infrastructure yet devolve into antagonstic squabbles regarding the color of said shed.
e.g. http://www.bikeshed.com/