5 ms·
Right. The hard line on this comes from aerospace. If A won't connect to B, you check the spec. If A isn't compliant with the spec, A is wrong and the vendor of
by Animats 5y ago
Right. The hard line on this comes from aerospace. If A won't connect to B, you check the spec. If A isn't compliant with the spec, A is wrong and the vendor of A has to fix it. Same for B. If you can't tell who's wrong from the spec, the spec is wrong. This is why you can unplug a Pratt and Whitney engine from a aircraft and plug in a Rolls-Royce engine.
Now, this worked a lot better when aerospace companies and the USAF had real clout with manufacturers. If it wasn't in compliance with the spec, you put a red tag on it and rejected it. The supplier didn't get paid.
The way it works today is that if the supplier is bigger than you are, it's your problem.
- drewcoo 5y agoAnd that kind of spec'ing and compliance is ultimately rooted in legal threats: loss of life leading to loss of money. Until software actively kills people (enough that it costs someone a lot of money), we won't see movement in this area.
- protastus 5y agoTo your point, most software comes with a license that says "this comes with no guarantee for any purpose, we are not liable under any circumstances". I remember reading licenses as a teenager and wondering about their legality.
- YeGoblynQueenne 5y agoThat's how computer hardware used to work: see "IBM PC". I have no idea if it still works that way. I haven't seen the insides of a computer for ages now. Hardware is constrained by the costs of manufacturing at scale. I can't make my own computer as I want it (can't find a hand-cranked punched-card reader, or a steam-powered dot matrix printer. Oh why). With software though, everyone can write whatever they like and send it out there were someone is bound to pick it up and reuse it. A little like the way Covid-19 spreads, I guess. No constraints, no respect for specs.
- javajosh 5y agoThe problem of software specification in that comprehensive sense is unsolved.