vor1968

No. It's like shooting yourself in the face because your friend survived it.

Is it possible to design a process that isn't a self-contained OS instance depending on a lot of horseshit overlay controls to perform a task in a well designed way that still allows privilege separation from the host OS in a manageable way?

Of course not. It's the basis for all this other shite.

These supervisor projects are always a chuckle.

Is anyone ignorant enough to believe that any monitor can survive general process failure or contribute to recovery of a system with abnormal function or resource starvation?

And that is the basic reason for these monitors! garbage. My last experience was with bluepill which was this mess of ruby nonsense. Anyone with any experience knows you can't trust a system to correct it's own failure. Why are we hammering this nail over and over to catch a 30% recoverable transient...management.

This type of thing would not have been an issue 15 years ago. This is Richard Stevens socket programming 101.