Option Z) Everyone vibe codes their own custom OS. Each implements and exposes only what they want. Hacker has to beat up on it online to find vulnerabilities. He finds one and he only owns that one machine.
There's probably some middle ground between A and Z, but monocultures are fragile. All eggs in one basket, potato famines, banana fungus, etc...
soon after that, the laid-off hackers become the next builders :)
circles. revolutions. until its learned to see whats ahead, then it can be diverted to something new
Option A is the best practices status quo for a lot of people. "Don't waste time and money reinventing the wheel", "Given enough eyes, all bugs are shallow", etc...
But Option Z is becoming cheap and fast, and given all the eyes, there still seem to be a lot of bugs in Option A.
Maybe it's better to tolerate a few bugs so long as it's not the same bug on everyone's computer.
Maybe you have fewer bugs if you aren't supporting 50 years of backwards compatibility.
Maybe the economics and risks change for the hacker when he can't find bugs offline.
Maybe we should appreciate people researching how to vibe code containers and kernels.
So it can very well be worst of bith worlds, worse security on actually homogeneous systems.
The dude who says, "Give me a microkernel, use QNX request/receive/respond for syscalls, it only runs WASM blobs, device drivers are isolated user mode processes, it only supports HTTPS on one network interface, and the file system is readonly ExFAT" will probably get something different.
I hate low value LLM prose (slop) too, but if you ask it to write like Herman Melville, you'll get few "it's not this, it's that".
Maybe you do still get the same kinds of errors when you ask for VMS, 64 bit memory safe DOS, or a Unikernel. I dunno, but it seems like something that could be improved when it's identified.
Ok, you have me intrigued. FreeDOS-64!
If the host's network driver is hacked, all userland is stolen too.
Someone more qualified than me can speak to isolating device drivers. I do know that one of the virtues of microkernels was supposed to be that you can run drivers unprivileged.
Sarcasm? Definitely not true, by several orders of magnitude. Have you seen how many built-in functions PHP has?
Just to clarify: I didn't mean the effort to find and fix a vulnerability in PHP (although that is also difficult). I meant the effort to reformat your system, investigate what else was compromised, and recover from backups after you get hacked through an exploit in PHP.
You probably don't use every last function, and you might be underestimating what became possible this year. You could have a model search for the features you use. You could have it loop until your existing code passes with the substitute. You could have it rewrite your code to use fewer features while still passing your existing tests.
I'm not saying you have to do this, but I think we should question which of our old approaches are based on old constraints.
(Better yet, just regular code it!)
Also this is like the worst case where the bug is in one monolithic piece of sw. Something like the alpine ssh bug is more relevant, you can plainly see not all systems are effected.
For security, GVisor is probably the most widely used userspace-kernel. A userspace kernel may also boot faster and use less resources as it can offload a lot of work to the host (FS drivers etc.)
Yes, I've tried using it before.