A "Bill of Lights" to Restrict LEDs on Gadgets?

PetManimal writes "Mike Elgan has had it with useless lights on gadgets and computers. He singles out the Palm Treo and the Dell XPS gaming laptops as being particularly bad with the use of unnecessary lights, and also cites the plethora of LEDs on desktop PCs and peripherals. 'My PC and other computing equipment make my office look like a jet cockpit. I have two LCD monitors, each of which has two indicator lights that flash even when the PC is turned off. The attached sound control has a light on it. My keyboard has multiple lights. The power cord has lights, the printer has lights, and the power button is illuminated. My cable modem and Linksys router flash like crazy all the time. Together, these useless lights create a visual cacophony of blinking, multicolored lights that make me feel like I'm taking part in a NASA stress test for astronaut candidates.' Elgan calls on manufacturers to respect his 'Gadget Bill of Lights' to restrict the use of nag lights and allow users to turn them off. He also says the industry should pay more attention to industrial design when creating new products."

Comments

Sharpie

[Nutsquasher]

Black marker is your friend, my man.

Re:Wow...

[Known Nutter]

totally.

I really hate the "more important things going on in the world..." argument, but damn man... this is total nonsense.

Besides, I like my office looking like a cockpit - the more flashing indicator lights, the better. One light I particularly enjoy is on my television. The indicator LED is ON when the tv is OFF, and OFF when the tv is ON.

I own a small roll of black electrical tape...

[Joce640k]

I own a small roll of black electrical tape...it only cost 50 cents and it works wonders on unwanted LEDs.

If only the colors made sense

[Animats]

There are proper NEMA color codes for indicators, and you'll see them on industrial equipment. Unfortunately, we went through a long period during which red LEDs were the only cheap color, and far too many red LEDs went onto equipment. Since LEDs are now available in all colors, it's time to go back to the traditional NEMA rules:

• GREEN - equipment normal, no action required.
• AMBER - abnormal condition, action may be required, but not immediate action.
• RED - trouble condition, action is required. No red light should be illuminated during normal operation. If you see a red light, something needs to be done about it immediately.
• BLUE - status indication, no specific meaning.
• WHITE - status indication, no specific meaning.

Anything that goes in a factory or a rack should obey those simple rules.

There is a good reason for this on some devices

[Targon]

You are one of those people who don't seem to understand why we NEED lights on routers. Routers can be(and often are) kept away from the computers and devices. In those situations, checking the router to see if the Ethernet cable is plugged in on the other end, or if data is being sent on that port are more important. So, green for link, blinking for data being sent/received. It makes sense, and isn't useless.

Many devices go to sleep, so all you have is a LED to indicate that the device is on. You would NOT want a device that doesn't have a power LED since it's nice to know when the thing is on or not, even if it is in sleep mode.

Yes, some devices are annoying in having too many blinking lights, and I really dislike the extra lights that are on some computer cases these days. But, you have to admit that there are times when having those bright lights is a real advantage.

So, devices with blinking lights are fine, but excessive numbers of "cute" lights isn't. On a positive note, you can generally turn off or unplug the extra lights on computer cases if you don't like them. Standby blinking lights are annoying, but will show you that the machine isn't really off by blinking.

If the power grid is so overloaded by all the devices that are in standby mode, then building some nuclear power plants should be done. There are obviously some places that those plants should NOT be located, such as in places there are earthquakes or that might be hit by a tornado, but that doesn't mean new ones should not be built. Let's get some power generation in place that doesn't require oil, and we will be in better shape.

Re:Wow...

[fyngyrz]

Lights: Routers don't have enough lights. They need bar graphs that tell me how much of the available bandwidth is being used (and what means that needs to be configurable in the on-board software.) A counter of currently expected reply packets might serve as a metric for "busyness" as well. And we should be able to configure the colors - R, G and B LEDS have been available for some time, lets get to using them.

Industrial design: Too many devices are "designed", looks-wise. What this means is some idiot decided that they should be really small, for starters. What this causes is the device being dragged all over by the cables attached to it, or being unable to sit flat without being glued or rubber-banded to something more substantial. Another "design" goal seems to be to create devices that look like they were squeezed out of an orifice, have only one flat side (the bottom) and as a consequence, won't stack. Another thing is means is that the indicators it does have are on the top or sitting at some weird angle, so you can't read them unless you are hovering over the bloody thing. First, make sure there is a front, and second, put the lights there. Third, make sure there is a back, and fourth, put the connectors there... or make the front double-high and put the connectors on the bottom, and the lights on the top (some devices call for ease of regular access, USB comes to mind here.) But I have routers and switches - for crying out loud - that have the channel status indicators right next to the jacks. You can't see half of them for the forest of cables that comes out of the devices. These would be fine if they were just there to tell you the cable is connected; but they are terrible for looking at the already set-up router and trying to get a sense of which lines are active and/or properly connected, and there are no other indicators to take on that role, so you're forced to dislodge cables to try and read the device status. Just dumb.

Power use: Make the lights switchable, absolutely. That way, you can turn them off, and I can leave them on. I hope to have the whole facility running on solar and wind power by the end of the year, but even if I didn't, those indicators serve a purpose that I am perfectly willing to pay for. An LED indicator isn't a big power user. I'm not going to get too excited about those kinds of drains.

Cable looms: If a device is meant to have a bunch (more than one) of cables plugged into it, it should provide an optional (meaning, you decide to attach and use it or not, but always supplied) cable loom so that you can redirect the cables from the front to the back, or vice-versa, according to your needs. This goes back to the "device is too light" design error; for instance, if you try to re-route 16 or 24 network cables, you're going to drag the device around by the tensions associated with bending all of those cables. If there is a loom, the device itself will keep the tension of the re-route from torquing it around.

More lights. The more something can tell me without requiring me to interact with it, the more time I save. A glance is always faster than calling up a web page and selecting some option.