We need another Bell Labs.
We need another Bell Labs.
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.
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.
Then, I for one, would not change C for anything else. The problem is not the language (which is just a tool), the problem is the coding (and the coders).
What does that mean? Like... small stdlib with everything moved to extra libraries? Languages don't really have a ring 0 so I'm not sure how to read this even though it feels like a maybe-interesting take
Instead, (parts of) programs should be restrictable to pure computation by denying any external resource access by default, unless explicitly granted or approved more (to the minimum they need, following the principle of least authority).
See: https://en.wikipedia.org/wiki/E_(programming_language) or any of the languages listed here: https://en.wikipedia.org/wiki/Object-capability_model#Langua...
Having a microkernel OS isn't really sufficient if you want to "hollow out the attack surface" well, because many programs (including imported libraries) consist of hundreds of thousands of lines of code made by hundreds or thousands of people (and now also AI). So programs should be internally compartmentalizable as well. Only this, imported libraries being able to sandbox their imported libraries and so on recursively truly reduces the possible effects of vulnerabilities to a minimum.
And only programming languages (or virtual machines i guess) can achieve these types of guarantees in a platform independent way.
What counts is not the mental model programmers build in their minds. It's the machine code that executes inside CPUs.
Case in point: https://hforsten.com/redefining-the-number-2-in-python.html
Add a zillion past, present and future supply chain attacks as examples too
The UNIX command line userland philosophy was not to architect a rigid user facing system in advance but enable ad hoc, as needed edge case problem solving.
Linus solved the problem of not having UNIX kernel sources by designing the Linux kernel from his experience as a UNIX user solving problems as they appeared not through advanced speculation and architecture. The connection seems obvious to me.
And this doesn't say anything that wasn't obvious this whole time. It's just in the spirit of the don't architect based on speculation but reality, LLMs didn't exist and didn't need to be accounted for. No corporation, nation state or script kiddie had enough compute back then.
This is all like config DSLs; it all been coming up again and again the entire 30ish I been paying attention to Linux/Unix.
Never contributed code back then though. I was more interested in EE, building electronics back then but was curious enough about Linux to build kernels and eventually Slackware. Really not all that interested in code today even; it's just how it works
Of course, I am talking about the kernel, not the entire OS.
Linux stood up on the shoulders of a giant like Minix, Unix was basically designed and coded from scratch.