4 ms·
For modernc you gave the correct link. For the wazero based driver, it's this package (I'm the author): https://github.com/ncruces/go-sqlite3 https://github.co
by ncruces 1y ago
For modernc you gave the correct link.
For the wazero based driver, it's this package (I'm the author): https://github.com/ncruces/go-sqlite3 https://github.com/ncruces/go-sqlite3
- Imustaskforhelp 1y agoYes btw if I may ask, how does the modernc code actually work and like, if I wanted my code to be minimalist, what should I rather pick? Also didn't expect that I would be talking to the author of wazero myself haha. I really admire your project.
- ncruces 1y agoI'm not the author of wazero, although I've been a maintainer. I'm just the author of the wazero based SQLite driver. modernc takes the SQLite amalgamation, runs it through the C preprocessor, then converts the result to Go file using the ccgo compiler. Not many further details on how that works: https://www.reddit.com/r/golang/comments/1apreer/comment/kqaa98u https://www.reddit.com/r/golang/comments/1apreer/comment/kqa... The Wasm version takes the same SQLite amalgamation and compiles it to portable Wasm using clang/wasi-sdk; the platform specific bits are implemented in Go. I'm not sure I can say which one is more minimalist with a straight face. One consists of mechanically generated, platform specific, 8MB Go files. The other embeds 1.5MB Wasm BLOB and needs wazero (a big dependency on its own).