News for hackers. Stuff that matters.
Re:Linux was created as a rejection of robust software archi... by privacyishuman on Sunday November 15, 2026 @10:58PM (#50513844)
Re:Linux was created as a rejection of robust software archi... by nxobject on Sunday November 15, 2026 @11:32PM (#50514069)
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".
Re:Linux was created as a rejection of robust software archi... by __MatrixMan__ on Sunday November 15, 2026 @11:32PM (#50514070)
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.

Re:Linux was created as a rejection of robust software archi... by wilsonjensen on Monday November 16, 2026 @12:18AM (#50514324)
> I don't think this is an accurate description of why linux was created.

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!"

Re:Linux was created as a rejection of robust software archi... by yjftsjthsd-h on Monday November 16, 2026 @12:38AM (#50514413)
> Yeah I think they're conflating UNIX-like general philosophy and Linux.

I don't think they are, actually; they appear to be arguing microkernel vs monolithic kernel, and we have unix-likes based on microkernels.

Re:Linux was created as a rejection of robust software archi... by grapheneos on Monday November 16, 2026 @01:37AM (#50514717)
Our posts were solely why it was created but rather the design choices made as part of building it from the beginning to the present day.
Re:Linux was created as a rejection of robust software archi... by notorandit on Monday November 16, 2026 @01:44AM (#50514745)
Yes, smaller and verifiable kernels would help a lot against buggy and malicious code. Let alone stability and robustness.

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).

Re:Linux was created as a rejection of robust software archi... by 7373737373 on Monday November 16, 2026 @01:51AM (#50514784)
Having languages themselves be built like microkernels would help security a hell of a lot too however
Re:Linux was created as a rejection of robust software archi... by yjftsjthsd-h on Monday November 16, 2026 @01:54AM (#50514799)
> Having languages themselves be built like microkernels

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

Re:Linux was created as a rejection of robust software archi... by 7373737373 on Monday November 16, 2026 @02:09AM (#50514900)
Yeah, currently popular languages don't have any separation, internal isolation, any way to limit or monitor authority (and use of that authority) to access and use resources at all. Programs usually have full ambient authority, meaning they can just name and use resources (importing libraries, stating file paths, ...) without restrictions.

Instead, (parts of) programs should be restricted to pure computation by denying any external resource access by default, unless explicitly approved, to the minimum they need (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", because many programs consist of hundreds of thousands of lines of code. 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 exploits to a minimum.

Re:Linux was created as a rejection of robust software archi... by yjftsjthsd-h on Monday November 16, 2026 @02:15AM (#50514931)
Oh, you want an object-capability language; I didn't connect those dots. Yes, that would be an excellent compliment and now that you've spelled it out I can see the analogy.
Re:Linux was created as a rejection of robust software archi... by notorandit on Monday November 16, 2026 @02:30AM (#50515017)
It does not mean anything to me.
Re:Linux was created as a rejection of robust software archi... by 7373737373 on Monday November 16, 2026 @02:41AM (#50515073)
A language that can monitor and limit the effects of a program's components and isolate them against each other is strictly better than one that can't.

One example: https://hforsten.com/redefining-the-number-2-in-python.html

Add a zillion past, present and future supply chain attacks as examples too

Re:Linux was created as a rejection of robust software archi... by wilsonjensen on Monday November 16, 2026 @03:24AM (#50515297)
I struggle to see a meaningful difference.

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.

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 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 and building electronics back then but was curious enough about Linux to build kernels and eventually Slackware. I digress.

Re:Linux was created as a rejection of robust software archi... by notorandit on Monday November 16, 2026 @01:40AM (#50514730)
Unix ans Linux are 20+ years apart with all the changes that happened to hardware, software and even to C: they could hardly have the same general architecture.

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.

Re:Linux was created as a rejection of robust software archi... by notorandit on Monday November 16, 2026 @01:15AM (#50514593)
Not even that, IMHO.

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.

Re:Linux was created as a rejection of robust software archi... by grapheneos on Monday November 16, 2026 @01:36AM (#50514708)
Our post never said anything about why Linux was created. We're talking about the design choices.
Re:Linux was created as a rejection of robust software archi... by zombot on Monday November 16, 2026 @02:12AM (#50514913)
That looks like a distinction without a difference to me.
Re:Linux was created as a rejection of robust software archi... by yjftsjthsd-h on Sunday November 15, 2026 @11:43PM (#50514131)
> 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?

Re:Linux was created as a rejection of robust software archi... by margalabargala on Monday November 16, 2026 @12:48AM (#50514458)
Arguably the only reason GOS is relevant is because they do exactly what you criticize them for.

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?

Re:Linux was created as a rejection of robust software archi... by yjftsjthsd-h on Monday November 16, 2026 @12:55AM (#50514491)
> 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.

Re:Linux was created as a rejection of robust software archi... by grapheneos on Monday November 16, 2026 @01:53AM (#50514792)
You're falsely accusing us of what you're doing. You lie about what we've said and done. Your posts contribute no value to this discussion. It's clear you can't participate in threads about GrapheneOS in a constructive way and should stop.
Re:Linux was created as a rejection of robust software archi... by yjftsjthsd-h on Monday November 16, 2026 @01:59AM (#50514839)
We are literally having this conversation because you opened with

> 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.

Anytime anyone mentions other ROMs like LineageOS you immediately jump in to proclaim them insecure. The shoe fits. If you don't like being called out for slinging mud at other projects including those that your project is built on, feel free to stop doing it.

Re:Linux was created as a rejection of robust software archi... by grapheneos on Monday November 16, 2026 @02:11AM (#50514906)
We were participating in a discussion about a discussion with high importance to protecting people's privacy and security. You're participated in threads about GrapheneOS in bad faith misrepresenting and directly lying about what we've said and done. You're continuing vile personal attacks on our team including continuing to try to portray as being insane and delusional as you've done many times before. You aren't contributing anything constructive to discussions about it but rather are trying to use it as a platform to harm the project and our team.
Re:Linux was created as a rejection of robust software archi... by yjftsjthsd-h on Monday November 16, 2026 @02:37AM (#50515052)
(I'm going to ignore the wild personal attacks in this comment.)

> We were participating in a discussion about a discussion with high importance to protecting people's privacy and security.

Okay? How do you get from there to

> Linux was created as a rejection of robust software architecture and tools.

?

Like, the rest of this is completely reasonable and (materially) correct:

> 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.

If you'd written "Linux was created when hardware was weaker so it made trade-offs against security" I wouldn't mind. If you said "Linux was created to favor performance over security" I'd quibble a little but that'd be a reasonable argument. If you'd just said "Linux prefers performance over security and we prefer the opposite so we're investigating a migration to seL4" I'd agree and be super interested. Why would you jump straight to "a rejection of robust software architecture and tools"? What productive discussion is going to come from that?

Re:Linux was created as a rejection of robust software archi... by rendaw on Monday November 16, 2026 @01:38AM (#50514721)
I think most users of GOS don't have a stick by which to measure the security claims of GOS. And I'm guessing most are there for privacy, not security.
Re:Linux was created as a rejection of robust software archi... by sidm0623 on Monday November 16, 2026 @01:55AM (#50514806)
Im pretty sure GOS is based of Android which is based off Linux. Where are you getting Minix from?
Re:Linux was created as a rejection of robust software archi... by grapheneos on Monday November 16, 2026 @01:56AM (#50514816)
You're lying about what we've said and done. You're lying about what we've built and are building. Your posts in discussions about GrapheneOS are irrational attacks on the project. You post in threads about it maliciously to attack the project and team in any way you can. You've consistently engaged in vile personal attacks towards our team and supported harassment. You're referencing those things here.
Re:Linux was created as a rejection of robust software archi... by 7373737373 on Sunday November 15, 2026 @11:44PM (#50514134)
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 with its capability-based addressing should have succeeded earlier too.

Re:Linux was created as a rejection of robust software archi... by yjftsjthsd-h on Sunday November 15, 2026 @11:55PM (#50514192)
> 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...

Re:Linux was created as a rejection of robust software archi... by 7373737373 on Monday November 16, 2026 @12:04AM (#50514254)
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.

Re:Linux was created as a rejection of robust software archi... by anonymous908213 on Monday November 16, 2026 @12:30AM (#50514373)
Software has become doubly bad at the same rate that hardware has become doubly good, so we by no means have compute to spare. A 2x slowdown would absolutely be unacceptable. No business is going to pay for twice as much compute on their servers. No developer is going to pick the OS that takes 30 minutes to compile a large Rust program instead of 15 minutes. If you get double the performance for the same cost, it's not even a contest.
Re:Linux was created as a rejection of robust software archi... by 7373737373 on Monday November 16, 2026 @12:40AM (#50514422)
To me this looks like a world rushing toward catastrophic failure

Security isn't just a word, it's the security of the world as technology becomes ever more integrated and influential in it

Re:Linux was created as a rejection of robust software archi... by anonymous908213 on Monday November 16, 2026 @12:45AM (#50514447)
I don't disagree that security is important, but you need a better pitch than "give up half of your compute for security" for a general-purpose OS, because the reality is nobody's buying with a sales pitch like that and you need a pitch that people will actually buy if you want to see that security manifest in the real world.
Re:Linux was created as a rejection of robust software archi... by showlife on Monday November 16, 2026 @01:36AM (#50514709)
The better pitch is "give up half of your compute for security or give up all of your compute when your company is forced to shut down because of a security incident." Almost all of the work I do is patching or managing the orchestration that facilitates that patching. If my employer didn't think they had to pay me to do this I'm sure they wouldn't!
Re:Linux was created as a rejection of robust software archi... by hollerith on Monday November 16, 2026 @02:08AM (#50514890)
I’d gladly give up half of the compute on my devices for security if given the option.
Re:Linux was created as a rejection of robust software archi... by yjftsjthsd-h on Monday November 16, 2026 @02:16AM (#50514939)
Sadly no real mobile equivalent, but you might consider qubes-os on PC.
Re:Linux was created as a rejection of robust software archi... by hollerith on Monday November 16, 2026 @02:38AM (#50515056)
I haven’t installed Qubes out of doubt that they can continue to maintain it for long. The whole cloud has settled on Firecracker for sandboxing VMs whereas Qubes picked Zen. And Qubes has only started moving to Wayland.
Re:Linux was created as a rejection of robust software archi... by yjftsjthsd-h on Monday November 16, 2026 @12:37AM (#50514402)
I am fairly confident that you would find that most people, if offered the chance to take that performance hit in exchange for some security improvement, would not take the deal so quickly as you. Since this is (somewhat) in the context of mobile, I also have to point out that it's also going to be a battery hit and that might be an even harder sell.
Re:Linux was created as a rejection of robust software archi... by robotresearcher on Monday November 16, 2026 @12:41AM (#50514426)
We spent the cycles on Python and web apps. None left for security.
Re:Linux was created as a rejection of robust software archi... by ptidhomme on Monday November 16, 2026 @02:28AM (#50515002)
> a 2x slowdown would be unacceptable, [...] in exchange for a system that doesn't allow thousands of vulnerabilities

OpenBSD fits the bill

Re:Linux was created as a rejection of robust software archi... by pjmlp on Monday November 16, 2026 @01:26AM (#50514656)
Yes, it works alright for Windows, macOS, iOS, iPadOS, Android, Fuchsia.

And all those cars, rockets, factories powered by QNX, INTEGRITY,....

Ah, and those Switch games, nothing really that relevant.

Re:Linux was created as a rejection of robust software archi... by yjftsjthsd-h on Monday November 16, 2026 @01:49AM (#50514772)
> Yes, it works alright for Windows, macOS, iOS, iPadOS, Android, Fuchsia.

Other than Fuchsia (I assume), all of those are at most hybrid systems with the performance-sensitive drivers still in ring 0.

> And all those cars, rockets, factories powered by QNX, INTEGRITY,....

Yes, you can get away with a lot if you're willing to sacrifice performance for safety.

> Ah, and those Switch games, nothing really that relevant.

That actually is an interesting point. Do you know how that works? I'd guess either they're doing something fun in hardware or they've actually got something going on in software worth considering. (Unless the thing they're doing is impractical to port to more general-purpose systems)

Re:Linux was created as a rejection of robust software archi... by pjmlp on Monday November 16, 2026 @02:38AM (#50515055)
> Other than Fuchsia (I assume), all of those are at most hybrid systems with the performance-sensitive drivers still in ring 0.

Not really.

Apple iDevices don't allow third parties to ship drivers to ring 0, all third party drivers are in userspace.

While macOS still allows for kexts, the official roadmap is that ring 0 is only for Apple, everyone else has to move into userspace drivers.

Android only allows ring 0 drivers for "legacy" Linux kernel drivers, all other drivers must use Android IPC since Android 8.

Windows 11 runs on top of Hyper-V, drivers run virtualised (Device Guard) and do several key kernel components (Secure Kernel), everything together is known as Virtualization-Based Security.

These features are also available on Windows 10, however there they need to be explicitly enabled.

Additionally, since Windows 8 several drivers have been pushed into UMDF, and since the whole fallout in 2024, that there is a new framework on the way for security folks to take their stuff out of the kernel.

Across all three vendors, the amount of application sandboxing keeps going beyond a plain Flatpak or Snap can do, and there is a lot more going on with XPC, Android IPC, COM (out-proc) than D-Bus gets used for.

Horizon works, because Nintendo is not doing Minix, like everyone does when they talk about microkernels, rather taking the lessons out of operating systems like QNX on how to pass capabilities around.

https://news.ycombinator.com/item?id=17534593

Re:Linux was created as a rejection of robust software archi... by fsflover on Monday November 16, 2026 @03:30AM (#50515338)
Qubes OS uses type I hypervisor with hardware virtualization to provide security through compartmentalization. The performance hit is minimal.
Re:Linux was created as a rejection of robust software archi... by huijzer on Sunday November 15, 2026 @11:48PM (#50514151)
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++).
Re:Linux was created as a rejection of robust software archi... by guywithahat on Sunday November 15, 2026 @11:55PM (#50514193)
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
Re:Linux was created as a rejection of robust software archi... by grapheneos on Monday November 16, 2026 @01:44AM (#50514748)
None of the core Linux kernel or drivers are written in Rust. Drivers can theoretically be written in Rust but there's immense resistance to landing the bindings needed to do it. In practice, a few core Android drivers were ported to Rust and in very rare cases new drivers for a previously unsupported GPu, etc. are using it.
Re:Linux was created as a rejection of robust software archi... by guywithahat on Sunday November 15, 2026 @11:53PM (#50514185)
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

Re:Linux was created as a rejection of robust software archi... by 7373737373 on Monday November 16, 2026 @12:16AM (#50514316)
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.
Re:Linux was created as a rejection of robust software archi... by grapheneos on Monday November 16, 2026 @01:48AM (#50514764)
Microkernels are incredibly widely used. They're used on many of the components used in a modern computer including radios for cellular, Wi-Fi/Bluetooth, GNSS, NFC, etc. Many components are now written in a more secure way than mainstream general purpose operating systems. macOS and iOS have also gradually been moving more towards microkernel design by moving code out of the kernel. They started from a foundation where that was part of the design but not heavily used.
Re:Linux was created as a rejection of robust software archi... by zbentley on Monday November 16, 2026 @12:31AM (#50514379)
The main reason Linux succeeds is network effects. Once everyone has been coding to Linux/POSIX APIs for upwards of 35 years, the ability to move to something else is incredibly limited. Even if a new OS attracted 100% mind share for all new development, it'd take many, many years for it to approach even the beginnings of ubiquity that Linux had in the early 2000s.
Re:Linux was created as a rejection of robust software archi... by grapheneos on Monday November 16, 2026 @01:49AM (#50514774)
Replacing the Linux kernel ABI isn't necessary to have a microkernel written in a memory safe language. It can provide the same ABI. gVisor is not what we mean but shows it's doable.
Re:Linux was created as a rejection of robust software archi... by pjmlp on Monday November 16, 2026 @01:27AM (#50514666)
If they had to actually pay for Linux, I doubt it.
Re:Linux was created as a rejection of robust software archi... by qalmakka on Sunday November 15, 2026 @11:55PM (#50514196)
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.

Re:Linux was created as a rejection of robust software archi... by zombot on Monday November 16, 2026 @02:08AM (#50514893)
> it's likely going to fail in the end.

If it had been given half a chance, this would be true. But not even trying is not the same as failing by a long shot.

Re:Linux was created as a rejection of robust software archi... by leonidasrup on Monday November 16, 2026 @02:48AM (#50515112)
NeXTSTEP uses the Mach kernel, the predecessor to XNU

https://en.wikipedia.org/wiki/Mach_kernel

Re:Linux was created as a rejection of robust software archi... by nromiun on Monday November 16, 2026 @12:10AM (#50514291)
> 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 is very easy to imagine something rather than creating it in reality.

Re:Linux was created as a rejection of robust software archi... by pjmlp on Monday November 16, 2026 @01:32AM (#50514692)
Linux only mattered to me in 1995, because doing the UNIX work assignments from the university DG/UX and Solaris timesharing servers wasn't possible on the joke of Windows NT POSIX subsystem.

Had Microsoft been serious about their POSIX support, I would not have bothered one second.

It wasn't FOSS nor hardware support, rather not having to travel to campus laboratory and fight for a terminal, losing a couple of hours.

Re:Linux was created as a rejection of robust software archi... by lordkrandel on Monday November 16, 2026 @12:17AM (#50514319)
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
Re:Linux was created as a rejection of robust software archi... by dang on Monday November 16, 2026 @02:03AM (#50514861)
Can you please follow the site guidelines when posting here, regardless of how wrong someone else is or you feel they are?

https://news.ycombinator.com/newsguidelines.html

Re:Linux was created as a rejection of robust software archi... by somat on Monday November 16, 2026 @12:20AM (#50514332)
Unix itself was created as a rejection of robust software architecture and tools.

"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" collages: 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.

Re:Linux was created as a rejection of robust software archi... by marcus_holmes on Monday November 16, 2026 @12:31AM (#50514381)
"you either die a <minimal hackable low cost OS> or live long enough to become a <huge enterprise OS>"
Re:Linux was created as a rejection of robust software archi... by dvrp on Monday November 16, 2026 @12:45AM (#50514446)
“You either die a LISP, or live long enough to become JavaScript”
Re:Linux was created as a rejection of robust software archi... by HexDecOctBin on Monday November 16, 2026 @01:32AM (#50514689)
Which is funny, considering the size of CL spec.
Re:Linux was created as a rejection of robust software archi... by pjmlp on Monday November 16, 2026 @01:23AM (#50514639)
Lets remind ourselves that initially, DoD assigned an higher security score to Multics than UNIX, with PL/I proper strings and arrays, with bounds checking available (configurable), as one of the key reasons.
Re:Linux was created as a rejection of robust software archi... by zombot on Monday November 16, 2026 @02:06AM (#50514874)
And now 50 years of "worse is better" come home to roost, with a vengeance.