While not perfect, with their own set of issues, macOS/iOS, Windows (with .NET/UWP) and Android are a couple of steps into that direction.
Interesting that you refer Plan 9, but fail to mention Inferno, which was the final vision from the same researchers.
Regarding UNIX, one thing that keeps being missed regarding NeXTSTEP and its derived OSes, and to go along your remark, it that for NeXT and Apple, UNIX wasn't never relevant.
The UNIX compatibility was just a means to bootstrap the OS and attack the UNIX workstation market, the Objective-C technology stack (now Swift as well) was/is where the real value of the OS was.
Anyone using macOS or nowadays WSL as UNIX replacement, is replicating the farmer's story from the talk.
For the lazy like me:
I bet not many professors bother to dive into it.
The documentation is still available, http://doc.cat-v.org/inferno/4th_edition/, and you can get it as open source and commercial variants, http://www.vitanuova.com/inferno/
So it is mostly a matter of actually caring to dive into it.
Not only one will discover how many of the Plan 9 design issues got worked on, some of the design ideas that went into Go will be more clear.
It is also revealing to dive into Oberon OS linage and then see how some of its design went into ACME on Plan 9, dynamic loading on Inferno or eventually Go's method call and unsafe package design.
Instead most get off at the Plan 9 train station.
Since we're at it, I'd add: Amiga. And I'm not sure, but maybe AREXX also deserves a mention too.
To my knowledge there haven't been any outstanding innovations on the software side that haven't been available in other operating systems too, but it did so in a computer that was 10..100x cheaper than a UNIX workstation with a comparable graphical user interface.
AmigaOS was more like a stripped down UNIX (preemptive scheduling, but no memory protection/process isolation), MacOS looked like a toy in comparison to be honest, at least from the technical side.
In the later years, AmigaOS (or rather its applications) offered a glimpse into a future how applications and the underlying operating system could work together to create a professional working environment, applications didn't feel isolated, there were standards in place how UI applications can be controlled from the command line, how they can be automated through scripting, how applications can talk to each other, and how they can be extended via operating system plugins (for instance if one application added support for a new image format to the operating system, all other application dealing with images automatically gained support for this new image format too).
Basically: how can the straightforward automation from the command line brought into the domain of UI applications.
Alas, it was a glimpse into a future that would never happen.
With exception of SGI and NeXT, UNIX never had a multimedia culture.
BTW, I'm curious what you think about the question I asked in https://news.ycombinator.com/item?id=22083468
Tools like ARexx and Amiga Basic were better (IMO) than what you got on other platforms, but the OS itself was rather meh. I guess you could say it was rather interesting in the sense that it had preemptive multitasking (years before PCs and Macs would) without memory protection... but that's hardly something you'd want to carry forward to present day.
Isn't linux advancing in similar direction, except that everything is a file descriptor (even processes are now!) instead of a file bound to the directory tree? And technically, everything that is a file descriptor is also a file, thanks to procfs.
This should also go hand in hand with development in alternative computing systems, environments, and architectures as well. Just as the dominance of Unix occurred in part for social/economic/cultural reasons, so too did the current dominant computing architectures. We have examples from the past of interesting attempts (i432, Rekursiv, maybe Oberon etc).
Because we have universal data interchange standards today (think XML structures, JSON, hell even TCP/IP itself) we don't have to worry as much about the "compatibility" issues that were a real end user problem in the 80s and 90s. We can and should be experimenting with alternative systems. Maybe open hardware will also help with that.
> alternatives to C and C++ such as Python, Rust, Go, Clojure, Haskell, Swift
Please advise me. I am just writting a kernel module for hooking kernel calls and I really """hate C""", I would love to do it in python (even better in js or vbscript, logo also comes to my mind - i just love driving a turtle). The input is python, the output .ko.
And as normal for kernel module it needs to be rock stable and as fast as possible as the hooked functions are called a lot on the system and cant loose much time there.
Can you share a sample please? I am thinking of doing it in bash script by emitting opcodes directly but it seems like it just take too long to dig out all opcodes. Yeah, I know what you think, but it is not assembly, it is bash script.
/sarcasm off
I for one get dots when keep seeing people with lack of vision.
/sarcasm ooooooooofffffff
C isn't the only game in town.
BSD is becoming irrelevant in world at large, so that would just be a waste of time.
In any case, the bazaar has proven that it is only technically able to produce UNIX clones.
edit: found a version with better camera angles
This talk is much better but some of his criticism are rather pointless because what he wants is a complete new OS design vastly different from UNIX. If he likes Windows/MacOS so much he should just use that.
The basic answer I get when asking this is 'because hardware has changed' which is obvious but avoids the question. Sometimes someone will bring up vector instructions are supported in rust but for a large portion of programming you don't want to vectorize (seriously measure what you think you need to vectorize). Ideally a compiler could compile $lang to word at a time aka SWAR if needed.
Another thing that I'm curious about is how much familiarity the speaker has with Plan 9? Plan 9 from Bell Labs is the spiritual successor to Unix, created by many of the Bell Labs researchers who originally worked on Unix. The creators of Plan 9 pushed "everything is a file" to its limits. Sadly, although I have read some Plan 9 papers, I haven't actually used the operating system. I'm really curious about what the USB example in this talk would look like in Plan 9?
I do wish there was more development in alternative operating systems. I like Unix, but there were many ideas from VMS, Smalltalk, the Genera operating system for Symbolics LISP machines, the classic Mac OS, BeOS, Plan 9, and other operating systems that we can learn from and that would be very useful to have today. Also, today's hardware is quite different from the hardware of 50 years ago. We have multi-core CPUs, GPUs with hundreds of cores, very fast NVMe storage devices, and other amazing technologies. There has also been much advancements in programming languages, with more people willing to explore alternatives to C and C++ such as Python, Rust, Go, Clojure, Haskell, Swift, and many more, each providing different abstractions for dealing with diverse programming tasks. I wonder what an operating system for the 2020s would look like given the advances in technology and the lessons learned in the past decade.