4 ms·
The cardinal sin of computer science was a failure to understand the importance of defining and enforcing interfaces at module boundaries. The most successful
by ethbr0 6y ago
The cardinal sin of computer science was a failure to understand the importance of defining and enforcing interfaces at module boundaries.
The most successful project (internet + web) did a much better job.
But legacy wise, we have a breakdown of boundaries at so many levels of the stack.
- bluepizza 6y agoBut there wasn’t really any other option back then, was there? Breakdown of boundaries meant squeezing more performance from both memory and CPU which were expensive and lacking.
- toyg 6y agoI’d take exception with the idea that internet/web did a better job of defining interfaces. The web equivalent of Unix (i.e. something we’ll probably never move from, and will haunt us forever) is Javascript.
- qwertywert_ 6y agoI think it's different because internet is literally interconnecting devices, some of which might not even be running an OS per say. Whereas Apple can release a new device on new OS with some custom hardware/drivers and as long as the internet + web parts are compatible with those interfaces there is no issue for customers. Maybe you're right though, but also isn't that what Posix was meant for? Also for things like Wi-Fi, they define those standards but the underlying vendor implementation is totally custom and can get really ugly still, just like an OS.
- ethbr0 6y agoThe true benefit of hard interfaces is enforcing modularity, and the benefit of modularity is being able to upgrade a system. (At minimum, emulate & migrate over time) Even "relatively" simple monolithic systems are nightmarishly complex to change. Apple doesn't really give a shit about backwards compatibility, past the bare minimum to keep their platform devs from revolting. POSIX, originally, was intended to provide a solution to every-vendor's-Unix problem. A nice side effect of it was absolutely that we got (mostly) standard interfaces.