4 ms·
What I don't get specifically is what's being implemented here with SQLite. Assuming WASI is an interface an application can call into for things like filesyste
by aargh_aargh 3y ago
What I don't get specifically is what's being implemented here with SQLite. Assuming WASI is an interface an application can call into for things like filesystem access, sockets, does this add SQLite as interface (analogously to sqlite.h) next to these as part of WASI? So SQLite will be "under" the interface, i.e. part of a standard runtime?
How much "batteries included" is this runtime (planned to be)? If I understood this correctly, then there would be a tradeoff with having more batteries included which would imply more functionality for applications but make porting to new targets more work.
- angelmm 3y agoThe main work behind this patch is to ensure that SQLite can compile to Wasm32-wasi. WASI doesn't offer all syscalls that SQLite may require, so it may require some conditional definitions and code to ensure it works properly. It doesn't mean that SQLite is part of WASI, but you can embed SQLite in a Wasm32-wasi module. In the future, the WASI standard will include more and more features. This will allow SQLite to enable more internal features that are currently skipped due to the limitations on WASI.
- aargh_aargh 3y agoAh, so it's SQLite running on top of WASI, as a user (application, or rather library). Thanks for clearing that up for me.
- angelmm 3y agoExactly! :D
- deleted 3y ago[deleted]