3 ms·
Cool idea! FWIW, when experimenting with stuff like that, I never had a good experience with WASM. It might be nice for “traditionally compiled” languages, but
by cube2222 2y ago
Cool idea!
FWIW, when experimenting with stuff like that, I never had a good experience with WASM. It might be nice for “traditionally compiled” languages, but for stuff like JS or Python (which is what you’d usually like to expose to users, rather than C++) it’s not that great of an experience, and at least for JS the runtimes aren’t compatible with common JS runtimes.
What I think is a bunch more promising in this area is Deno[0], which is a fully sandboxed-by-default JavaScript runtime, and as of Deno 2.0 recently is also compatible with Node APIs.
Based on the logos on their Subhosting[1] product landing page, they even seem to have a couple major companies using it for this very purpose.
[0]: https://deno.com/ https://deno.com/
[1]: https://deno.com/subhosting https://deno.com/subhosting
- Kinrany 2y agoDeno allows WASM as well!
- nilslice 2y agoYes, Deno Subhosting is very cool - but it’s still basically just an HTTP call to another service. Even if you self host it. XTP encourages you to actually run the user code _inside_ your own process - directly alongside your app code. This enables integrations with bidirectional capabilities that are just not possible with a network boundary between the host and guest.