3 ms·
Appreciate your support! We deliberately chose a limited runtime (quickjs + some shell applets). The tool parameter constraint enforcement was more important to
by souvik1997 8mo ago
Appreciate your support! We deliberately chose a limited runtime (quickjs + some shell applets). The tool parameter constraint enforcement was more important to us than language completeness. For agent tool calling, you don't really need NumPy and Pandas.
Wasmer is doing great work—we're using wasmtime on the host side currently but have been following your progress. Excited to see WASM sandboxing become more mainstream for this use case.
- syrusakbary 8mo ago> For agent tool calling, you don't really need NumPy and Pandas. That's true, but you'll likely need sockets, pydantic or SQLAlchemy (all of of them require heavy support on the Wasm layer!)
- souvik1997 8mo agoFair point. We get around this by "yielding" back from the Wasm runtime (in a coroutine style) so that the "host" can do network calls or other IO on behalf of the Wasm runtime. But it would be great to do this natively within Wasm!
- syrusakbary 8mo agoMight be worth taking a look at WASIX [1] We implemented all the system calls necessary to make networking work (within Wasm), and dynamic linking (so you could import and run pydantic, numpy, gevent and more!) [1] https://wasix.org/ https://wasix.org/
- souvik1997 8mo agoWe will take a look! Thanks for sharing. Dynamic linking to run pydantic/numpy/etc. would be huge!