Skip to content
This repository has been archived by the owner on Nov 22, 2018. It is now read-only.

Alternative approach #18

Open
andrewchambers opened this issue Aug 14, 2018 · 2 comments
Open

Alternative approach #18

andrewchambers opened this issue Aug 14, 2018 · 2 comments

Comments

@andrewchambers
Copy link

andrewchambers commented Aug 14, 2018

Consider you compiled sqlite to wasm and then run it under a wasm interpreter https://github.com/perlin-network/life and implemented the sqlite https://www.sqlite.org/vfs.html interface in go.

Not saying one way is better or worse, just a consideration, depending on how difficult the compilation from C is.

edit: from the current state of wasm, you would need one wasm VM instance per sqlite connection.

@cznic
Copy link
Owner

cznic commented Aug 14, 2018

Thanks for the idea. It sounds interesting but it's improbable I would have the resources to explore it any time soon. But considering C to wasm compilers do already exist, IINM, it could be a lot of fun for someone else to try out. In any case thanks for bringing github.com/perlin-network/life to my attention, I haven't heard about it before.

@andrewchambers
Copy link
Author

Indeed, your libc project is interesting, generalizing the approach could be decent to bring lots of C libs and interpreters to pure go at least from the end users point of view. Maybe a good experiment for another day.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants