I'm making a whole new language to get around the problem you're talking about: it brings no runtime at all. One of my targets is a Sandstorm like system I've been slowly working on, but I'd love for it to be a fit for the actual Sandstorm successor.
And I’m assuming your worker runtime is a process in a container on a shared node? What happens if the agent exploits your runtime?
Does it get access to the whole container? VM? Node?
Why should I ever choose this over MicroVMs? I have to design my architecture around your JS runtime. This isn’t an OS.
> WARNING: workerd is not a hardened sandbox
> workerd tries to isolate each Worker so that it can only access the resources it is configured to access. However, workerd on its own does not contain suitable defense-in-depth against the possibility of implementation bugs. When using workerd to run possibly-malicious code, you must run it inside an appropriate secure sandbox, such as a virtual machine. The Cloudflare Workers hosting service in particular uses many additional layers of defense-in-depth.
Sandstorm was great because it did proper sandboxing. This is pretty weak by comparison.