3 ms·
The things in this list are clearly mistakes. They aren't optimised, evolved solutions. They've just stuck around due to network effects. Nobody would design a
by IshKebab 3y ago
The things in this list are clearly mistakes. They aren't optimised, evolved solutions. They've just stuck around due to network effects.
Nobody would design a process spawning API like fork/exec today.
- thesuperbigfrog 3y ago>> The things in this list are clearly mistakes. They aren't optimised, evolved solutions. They've just stuck around due to network effects. Hello, JavaScript: https://www.destroyallsoftware.com/talks/wat https://www.destroyallsoftware.com/talks/wat https://youtu.be/D5xh0ZIEUOE?si=HTWxo0rM7y26mlpC https://youtu.be/D5xh0ZIEUOE?si=HTWxo0rM7y26mlpC Why are we waiting so long for WASM to replace JavaScript? https://www.destroyallsoftware.com/talks/the-birth-and-death-of-javascript https://www.destroyallsoftware.com/talks/the-birth-and-death... It's a similar story. Bad designs (perhaps they were reasonable given the circumstances?) that were set in stone due to network effects.
- Affric 3y agoMistakes? The thing about evolving design is that the environment changes. Fork/exec is fairly ergonomic compared to CreateProcess. Very few parameters. From a time when programs were small and security was simple. No design is immortal but just because it’s time is over doesn’t mean it is a mistake.