3 ms·
It would suck. We've been there before - older OSes like VMS were a lot more feature-rich and expected deeper integration from their applications. But the Unix
by lmm 3y ago
It would suck. We've been there before - older OSes like VMS were a lot more feature-rich and expected deeper integration from their applications. But the Unix "worse is better" approach won out. I think it's a similar effect to "the standard library is where modules go to die": the more functionality gets put in the OS, the slower it can be iterated on. So however cool what you originally build into the OS is, it gets lapped by what eventually gets implemented by loosely coupled userspace programs.
- tomrod 3y agoHyrum's law to the extreme. Adding anything in OSes tend to have users that rail against breaking changes.
- retrac 3y ago> But the Unix "worse is better" approach won out. Did it? In my opinion, modern Unix systems are much more like VMS than they're like traditional "worse is better" Unix. One of the classic "worse is better" interfaces is synchronous character IO. That is, to write a string, you call the write() routine repeatedly, sequentially, as you have things to write out. The call blocks the program until it completes. It's trivial to implement. It's a nice, easy-to-understand API from a programmer's perspective. It's also so terribly inefficient that every modern Unix has bolted on VMS-style asynchronous IO to replace it. Queues of transfer requests, where you design the full IO transaction, submit it to the OS, get an interrupt when it completes. More complex, unfriendly to the programmer, yet fundamental to getting real IO throughput from an operating system. Worse is better did not stand the test of time there.
- lmm 3y agoA few dedicated high-performance programs use those interfaces, but I wouldn't say they're mainstream, and they still seem to be oriented towards unstructured byte sequences and "everything is a file" as far as possible. And of course the highest-performance systems bypass the kernel entirely and do everything in userspace. OTOH one could make the argument that the pendulum is swinging back with things like dbus and overlayfs, or even modern linux sound APIs. So IDK.
- pjmlp 3y agoLooking to who's rulling desktop and mobile OSes, doesn't seem like UNIX did win. Yes there is a UNIX under macOS, and some POSIX under iOS/iPadOS/watchOS, Android, which hardly matters to userspace frameworks and official programming stacks. And naturally Windows is a kind of VMS reboot in spirit. UNIX only won on the server room, and even that seems to start to be irrelevant in the age of cloud computing and OS abstraction infrastructure.
- lmm 3y ago> Yes there is a UNIX under macOS, and some POSIX under iOS/iPadOS/watchOS, Android, which hardly matters to userspace frameworks and official programming stacks. On the contrary, the fact that more and more of the parts where development happens shifts further and further into userspace is exactly what I'm getting at.
- eternityforest 3y agoMaybe it won out on servers, but the world is mobile now, and mobile OSes are all about deep integration. Linux has some of it with DBus, and a lot of the coolest stuff is based on it, or some other standardized rich shared daemon like PipeWire, which is about as close as Linux can get to having a feature rich OS, since the kernel devs would never go for making it truly like Windows and all monolithic. The slower you iterate, the less you break, and the more focus you can have on app development rather than low level tool development. The time you waste on not quite that great stale APIs seems to be offset by the time you save not constantly fixing stuff. I suspect that the larger an app gets, the more it benefits from stability, because a million line app is probably going to have more code that nobody has needed to touch for 8 years