How would it work against vulnerabilities? You still put php inside, and it handles your data. When php is hacked, all your data is stolen, it doesn't matter that your OS is slightly different.

If the host's network driver is hacked, all userland is stolen too.

▲

yjftsjthsd-h 2 days ago | parent | next [-]

But if php is hacked and that's chained with a LPE, we'd like the attacker to get root inside a sandbox where that doesn't mean much.

▲

casualscience 2 days ago | parent | prev | next [-]

Php vulnerability depends on the rest of your system. E.g. imagine your system has strict sandboxing for PHP.

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.

▲

xscott 2 days ago | parent | prev [-]

I'm not sure any software is so valuable that you should never consider replacing it. Vibe coding a PHP substitute probably takes less time and tears than cleaning up a PHP exploit.

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.

▲

oasisaimlessly 2 days ago | parent | next [-]

> Vibe coding a PHP substitute probably takes less time and tears than cleaning up a PHP exploit.

Sarcasm? Definitely not true, by several orders of magnitude. Have you seen how many built-in functions PHP has?

	▲	xscott 2 days ago \| parent \| next [-]
		I sincerely try to avoid sarcasm. Communication is hard enough without it. 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.
	▲	2 days ago \| parent \| prev [-]
		[deleted]

▲

andai 2 days ago | parent | prev [-]

Forget PHP, just vibe code a substitute for the ten lines of WordPress you actually need.

(Better yet, just regular code it!)