hardware, don't talk to me about hardware...

Have I told you lately that I hate hardware? It too often seems to have been designed by the dumbest people on the planet, and that's when it's in working order, which isn't often enough.

too many crappy connectors

Serial cable wiring is the current bane of my existence, and Ethernet (since 10base-T) did do a much better job with connectors, but there's still far too much creativity with connectors. What's wrong with the good, old 8-wire RJ45 connector? Almost nothing needs more than 8 leads these days, yet I see a profusion of new connectors for every new whiz-bang. Does USB really need Yet Another New Incompatible Connector? Even when more leads are needed (e.g. SCSI), why do we have to have 4 or 5 different connectors, and why do they have to be such a pain to insert, especially in badly-lit corners?

There's a single universal generic power cord (at least in North America) with 3-prong connectors; I challenge the computer industry to get its data connectors down to one.

I continue to hope that wireless gizmos will enventually eliminate all data cables.

too many bizarro screw-heads

And why can't we have 001 screw-head designs? Who thinks up this rubbish, and why hasn't he been put to death yet?

hardware ``design''

The popular peripheral controllers don't seem have been debugged. Having to work around bugs in hardware shouldn't be necessary.

sleazy fans & power supplies

The leading cause of computer failures seems to be cheesy fans or power supplies that fail, causing the rest of the system to overheat. Is it too much to ask that vendors spend the few extra pence for reliable versions of these?

sleazy disks

IDE hardware is gradually becoming less stupid and it is dirt cheap, but disk manufacturers make their most reliable disks (as determined by QA testing) into SCSI disks, so IDE disks are pretty much guaranteed to die sooner than you'd like or expect.

ever-changing components

Even if you buy a board with the exact same model number as one you bought previously, the components may have changed in software-visible ways based on prices on the spot market the morning the board was made. And if the name or model number have changed at all, for example incrementing the version number or appending a letter or "Pro" or "Value Edition", ghod help you: the thing is likely to have completely new insides that are utterly software-incompatible with your earlier board.

A little honesty here would go a long ways: if you've changed the guts, say so by changing the name or number radically! Thinking you can paper it over by changing the Windows driver you supply doesn't cut it; we don't all run Windows.

programming documentation

It's incredibly hard to get documentation just on the programming interface to a board these days. See above re: Windows drivers not cutting it. The magic `Linux' word helps some, it's like Jedi mind control with some vendors. Decent documentation will sell boards, so it's worth a vendor's while to write it and give it away. It doesn't have to be fancy, just give us the theory of operation and what the bits in the registers do. This leads us into ...

the role of the evil Microsoft

Aside from general illegal monopolistic business practices, Microsoft has struck under-the-table deals with hardware vendors of the form `we'll write Windows drivers for your boards as long as you give your hardware documentation only to us'. One can only hope that Microsoft will get what it deserves, and soon.

themes

So the underlying problems seem to be: Apparently the responsible people don't realise the cost of cheapness and incompatibility. I'm here to tell them that they are great, and that short-term micro-optimisations are almost never worthwhile.
Geoff Collyer
geoff at collyer.net