80 ms·
IMO that article is the most damaging thing to happen to programming culture in 20 years. It's not hard to write a valid abstraction, and none of Joel's example
by lmm 5y ago
IMO that article is the most damaging thing to happen to programming culture in 20 years. It's not hard to write a valid abstraction, and none of Joel's examples actually hold up (yet he generalises it to a supposedly universal law). Of course abstractions are garbage-in, garbage-out - yes, TCP won't give you a reliable connection if you unplug the network cable, but an application written to use UDP won't fare any better in that case.
- tacitusarc 5y agoIt sounds like you completely missed the point he’s trying to make...
- lmm 5y agoMaybe, but if so so did many of my colleagues over the last ten years. I've seen so much bad code written in the name of avoiding abstractions, with that article as direct inspiration.
- klodolph 5y agoTCP won’t give you a reliable connection if you tunnel TCP over TCP, paradoxically, but you can tunnel TCP over UDP, UDP over TCP, or UDP over UDP. Leaky!
- lmm 5y agoNot "leaky", the conditions that a TCP connection needs its underlying transport to satisfy are explicitly documented, and TCP doesn't conform to them.
- klodolph 5y agoIf you're going into the details of what conditions a TCP connection needs, you're no longer talking about an abstraction.
- lmm 5y agoAn abstraction doesn't mean you can close your eyes and everything will work by magic. They're extremely useful tools, but like I said: garbage in, garbage out.
- klodolph 5y ago> An abstraction doesn't mean you can close your eyes and everything will work by magic. Right... that's why they're called "leaky abstractions". Because when you don't pay attention to the implementation details and their constraints, things break. If it weren't leaky, you'd call it a "specification" instead of an "abstraction".