A great pragmatical axiom of security is that if it doesn't come cheap in terms of speed and convenience, it's likely going to fail in the end. People will always pick practicality over security in the real world: if it takes too much time to lock and unlock the front door, the average person will just leave it ajar.
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.
I don't think this is an accurate description of why linux was created. But I do think it's time to design something that better fits the needs of the modern world.
I love this discussion, because it demonstrates what the market/developers actually care about.
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
I strongly doubt this is (still) true. Most devices are networked now. What is 10% less performance, in exchange for proper security? I would switch in a heartbeat. The only problem is that existing microkernel projects are not exactly usable yet. That their research, development and adoption are not more strongly funded and supported seems strange to me. As a programmer, OF COURSE i'd like to prefer to work with systems that gave me fine grained guarantees about resource (file system, network, CPU, memory) access, -isolation and -consumption.
> Linux was created as a rejection of robust software architecture and tools. It's a monolithic kernel with no internal isolation written as memory unsafe code. A typo in an obscure driver for unused functionality can easily create a fully privileged code execution vulnerability.
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.
Doh, a dude's opinion about something done completely for free as a hobbyist 30 years ago, that had world success, actually killing the robust corporate "only a lab can afford" alternative. Give yourself some peace
To be charitable, Linus initially called Linux "a hobby, won't be big and professional like GNU" and "NOT protable [sic](uses 386 task switching etc), probably never will support anything other than AT-harddisks".
> What's simplistic about it? The industry could have heavily adopted microkernels and memory safe languages 30 years ago.
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.
A great pragmatical axiom of security is that if it doesn't come cheap in terms of speed and convenience, it's likely going to fail in the end. People will always pick practicality over security in the real world: if it takes too much time to lock and unlock the front door, the average person will just leave it ajar.
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.
That most of the Linux kernel runs in https://en.wikipedia.org/wiki/Protection_ring 0 should have stopped decades ago
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.
> That most of the Linux kernel runs in https://en.wikipedia.org/wiki/Protection_ring 0 should have stopped decades ago
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...
I can't answer the hardware part.
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.
I don't think this is an accurate description of why linux was created. But I do think it's time to design something that better fits the needs of the modern world.
We need another Bell Labs.
https://xitter.cf/GrapheneOS/status/2122079826257588569#m
I love this discussion, because it demonstrates what the market/developers actually care about.
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
I strongly doubt this is (still) true. Most devices are networked now. What is 10% less performance, in exchange for proper security? I would switch in a heartbeat. The only problem is that existing microkernel projects are not exactly usable yet. That their research, development and adoption are not more strongly funded and supported seems strange to me. As a programmer, OF COURSE i'd like to prefer to work with systems that gave me fine grained guarantees about resource (file system, network, CPU, memory) access, -isolation and -consumption.
> Linux was created as a rejection of robust software architecture and tools. It's a monolithic kernel with no internal isolation written as memory unsafe code. A typo in an obscure driver for unused functionality can easily create a fully privileged code execution vulnerability.
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.
Doh, a dude's opinion about something done completely for free as a hobbyist 30 years ago, that had world success, actually killing the robust corporate "only a lab can afford" alternative. Give yourself some peace
To be charitable, Linus initially called Linux "a hobby, won't be big and professional like GNU" and "NOT protable [sic](uses 386 task switching etc), probably never will support anything other than AT-harddisks".
Linux was created around 1991. I think it has avoided many of the fads successfully so things could have been much worse (I’m looking at you C++).
I wouldn’t celebrate just yet they’re building some drivers in Rust now. I wouldn’t be surprised if in a few years Rust goes the way of Haskell
> What's simplistic about it? The industry could have heavily adopted microkernels and memory safe languages 30 years ago.
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.