> And then we'd have potential exploits both in the daemon and in the safe language runtime/compiler. That doesn't make the idea futile, especially considering

> And then we'd have potential exploits both in the daemon and in the safe language runtime/compiler. That doesn't make the idea futile, especially considering the current alternative. A language runtime focused on safety and a daemon that uses it for that purpose are going to present less of an attack surface than ifdef soup with custom malloc implementations and hand-managed buffer transfers.