Linux was created as a rejection of robust software architecture and tools
twitter.com
twitter.com
"I remarked to Dennis that easily half the code I was writing in Multics was error recovery code. He said, "We left all that stuff out of Unix. If there's an error, we have this routine called panic, and when it is called, the machine crashes, and you holler down the hall, 'Hey, reboot it.'"
-- Tom Van Vleck
Not that this is a bad thing, but unix was created as a hacker's toy, a small elegant system to play games on, This is why it is so fun to use. I mean, it is not really small or elegant anymore. but that is how it started, not as a robust correct business system. That is also why it got so popular. "A small hackable lowcost operating system with full source" colleges: yes please, and at a critical time in computing history, a very influential generation of hackers learned on it. Something now is better than perfect that does not exist, or that old cliche, worse is better.
Linux was a monolithic kernel because in 1991 microkernel were in earnest 25 years too early. Computers didn't really have the extra performance to spend for things like IPC and stuff. lots of other kernel designs that started back then like NT and Nextstep (was the NextStep kernel called XNU already? I guess not) all tried the microkernel route and then ended up doing stuff like networking at kernel level anyway because it just didn't work well enough.
arguably nowadays we have extra headroom to spare so stuff like containers, sandboxing, userspace drivers are becoming more and more commonplace.
Perhaps processor architectures like the https://en.wikipedia.org/wiki/Intel_iAPX_432 which do away with such coarse grained and therefore dangerous abstractions by using capability-based addressing should have succeeded earlier too. This is how modern programming languages should be structured too, instead of giving no guarantees to programmers (and therefore their users) about what (parts of) programs are able to access like they do now.
Do you have a way to do it on the hardware people actually have that doesn't destroy performance every time the CPU context switches? You can always move all your filesystems to FUSE if you like the performance...
But i'm perplexed by the unrelenting, ever re-occurring "counterpoint" of performance whenever the topic of sound security architectures comes up. As if even a 2x slowdown would be unacceptable, so many Moore's law doublings after Linux has been created later, in exchange for a system that doesn't allow thousands of vulnerabilities, and would limit the effects of more, yet undetected ones.
Security isn't just a word, it's the security of the world as technology becomes ever more integrated and influential in it
We need another Bell Labs.
Yeah I think they're conflating UNIX-like general philosophy and Linux.
The UNIX method has been shown to have many upsides.
Though implementations due to slow old computers without fancy GPUs are user hostile
It's all computer state so IMO applying the same concept and principle is more valuable a mindset than something more specific "Linux 4eva!"
I don't think they are, actually; they appear to be arguing microkernel vs monolithic kernel, and we have unix-likes based on microkernels.
The fact that we now have multi gigabyte RAM devices, does not mean that the kernel can go multi megabyte.
I'm also think that CPU designers should talk more to kernel developers: Linus is right on this topic.
Anyone who studies kernel development long enough will eventually say micro kernels are much safer, we have better languages now, or there are better ways to access OS resources, and they’re sort of right. But the reason Linux succeeds is because it focuses on being the fastest, fully featured kernel, and that’s what people actually wants. There are dozens of alternatives that nobody uses because at the end of the day, nobody cares if your language is “safer” and your drivers don’t have kernel access if it’s 10% slower when reading IO. They’ll just stick with Linux
Replacing Linux (and likely having to change some parts of POSIX as well) would be an even taller order than rewriting C code in some other language. At least for userland rewrites, you have parity and an API (POSIX, other libraries in userland) to code to.
It might still be a good idea to do both of those, mind you. But let's not fool ourselves: the main reasons the incumbents are the incumbents is that it's hard, likely-to-fail, and incredibly slow work to replace them.
Which is, of course, why GrapheneOS is based on minix, right?
Edit: Really, this is just GOS being GOS; only ever Security (by their own very specific, poorly defined definition thereof), with nothing else allowed to be a consideration. There is a reason the industry went with monolithic kernels when other options existed. Even today in 2026, we've merely worked out how to reduce the performance hit of microkernels, and in the 90s Torvalds was very justified in preferring to ship something that would actually run decently on extant hardware.
Edit2: To be fair. I like minix. I have actually tried to make HURD into a usable system. I want these things to work. But there are harsh tradeoffs in play that are still painful even after decades of work, and this kind of post does not exactly convince people that GOS is making level-headed evaluations of technical choices.
Lots of options exist for people who do what you describe as the "right" way. People who aren't in the security-at-all-costs group have plenty to choose from.
Are you saying that software that promotes security at the price of usability should not be permitted to exist, nor that people should, whatever their use case, desire it?
I'm saying maybe they could desire and work on their thing without having to constantly yell about how everyone and everything else is awful and sucks.
Ignoring the pesky little problem that these microkernels and languages did not exist 30 years ago. It was Linux with their garbage drivers that enabled people to use it in their computers. It is very easy to imagine something rather than creating it in reality.