The Successor to Research Unix Was Plan 9 from Bell Labs
theregister.com
theregister.com
I suspect that Plan 9 would be a more stable underlying OS for many places where Linux is used today, to include Android. I don’t know if it would be as efficient, but I really do question how much more important efficiency is than simplicity and correctness.
The sad truth is that users don’t care how simple software is to write. They do care about performance and battery life on their devices. The market chooses complex and fast over simple but slow. Every time - so long as any unnecessary complexity is hidden from users.
Simplicity buys you velocity, and velocity matters. But that’s a secondary effect.
No it doesn't. Developers and their employers choose slow and complex that saves them time in development, and customers choose things that exist over things that don't. They don't normally have much of choice between simple and complex.
> They don't normally have much of choice between simple and complex.
I also choose IntelliJ over Vim.
> I also choose IntelliJ over Vim.
Now do the same with your tram or parking ticket app.
I 100% want lean, fast software. But software being lean and fast is often at odds with it being simple. As an example, I’ve written a very complex realtime collaborative text editing library in rust that’s about 3000 loc. I’ve also ported the algorithm to JavaScript in about 500 lines. The JavaScript version is simpler by any metric - and it uses about 10x the ram and runs 100x slower than the optimised rust code.
My point is the rust code is better. It sounds like you may agree - at least in part.
There are plenty of places where Linux isn't the best solution (in engineering terms), nor is anything from the Unix extended family. But there's plenty of meta-engineering factors that make it "work".
UNIX would have been hardly as successful if AT&T had been allowed to sell it from the early days.
This is one reason that I feel that within a century or two, human-like beings will not be in control of this planet. Intelligent life will continue to evolve.
Popularity is a great heuristic for the individual - it means you'll find more examples, more tutorials, more help, more support, and others will beta test it before you get bitten. As a society, it's a prisoner's dilemma that we all keep defecting.
More like "paradox of voting"?
https://www.mdpi.com/2071-1050/13/15/8125#:~:text=A%20Rigoro.... ("Tragedy of the Commons is always a prisoner’s dilemma")
Quite the contrary, given that Microsoft Xenix was the most successful PC UNIX until Microsoft decided it wasn't worth pursuing UNIX on their portfolio.
Hardly did they knew how the server room would look like 40 years later.
http://doc.cat-v.org/plan_9/blue_gene/
https://www.researchgate.net/publication/225169133_Experienc...
Unix was developed to be the small and "dumb" computer's OS. But, because it instantly monopolized the communication protocols, it became impossible to replace. Only a system that was 100% compatible with Unix would be able to do so, and that would be just another Unix.
In retrospect, it's very strange that a lot of programmers think that Unix is a good OS, or try to learn from its design. It's kind of awful, even after a lot of increments that tried to remove the awfulness and polish some rough edges, it's still really bad. And it's also getting worse, as virtually all long-living software does because of bolted-on functionality that wasn't anticipated by the original design.
So yeah UNIX-like shell and POSIX APIs are needed due to the amount of existing software we have out there, but that is about it, we should really move beyond it, for anything that isn't a server or embedded headless device.
Part 4, the last part, coming soon, but it's more of an epilogue.
Part 1
Drowning in code: The ever-growing problem of ever-growing codebases
https://news.ycombinator.com/item?id=39356574
Part 2
Forgetting the history of Unix is coding us into a corner
Other than that, great article.
Yes, it is true, Microsoft did indeed have a Unix... But Xenix was a was a fairly obscure niche OS until SCO took it over & propelled it to greatness.
I deployed it in production in 1989 and we had no idea it had ever been an MS product. That was already forgotten.
> If we go way back in time, Microsoft was actually the first one to go to AT&T and beg to get a nice high-volume commercial license for Unix. And for many, many years we were the highest volume licensee, not only for our own Xenix products, but Siemens with theirs, Santa Cruz with theirs, and dozens and dozens of sub-licensees
-- https://web.archive.org/web/20010818203946/http://www.micros...
It is an important and very common error of thinking to assume that everyone has the same experiences as you. Don't think "because I did X and found Y, everyone that does X must find Y."
I too learned Unix on Xenix. I installed Xenix 286 on my IBM PC-AT in my first job, fitting a 2nd (15MB) HDD to do it (ST-506, 5.25" FH). I got it exchanging messages via UUCP with Xenix 386 over a serial line to a larger 386 machine that wasn't mine. This was 1988. Our office wasn't networked -- LANs were too new and too expensive.
No WWW, no internet, no Google. Before Linux, before 386BSD.
In my next job I took out my own personal online subscription, which I still have; that email address is now 33 years old.
I learned Unix from the SCO manuals, which were excellent. I fondly remember the Permuted Index.
No mention of Microsoft. Only occasionally in copyright messages, and they were everywhere and were meaningless and ignored. It would be decades later I discovered Xenix was originally an MS product. To me, it was a SCO product, and SCO were good guys.
SCO != SCO Group, who now have tainted the name and most people reading "SCO" don't know the difference.
But, for me, Xenix == SCO.