3 ms·
Performance is likely part of it. The WASM solution looks faster than modernc: https://github.com/cvilsmeier/go-sqlite-bench https://github.com/cvilsmeier/go-sq
by kyrra 2y ago
Performance is likely part of it. The WASM solution looks faster than modernc: https://github.com/cvilsmeier/go-sqlite-bench https://github.com/cvilsmeier/go-sqlite-bench
- ncruces 2y agoAuthor here. Faster was a by product. Maintainability was the goal. API coverage, ergonomics, extensibility all rank higher in my book than performance. An example I'd like to cite is sqlite-vec. Alex was able to build a Cgo-free version of it, on his own, which works fine with my bindings. This would be much harder to do with modernc. https://github.com/asg017/sqlite-vec-go-bindings https://github.com/asg017/sqlite-vec-go-bindings I'm also adding support for building off the bedrock branch (begin concurrent, wal2). You just build the branch with wasi-sdk, then embed the resulting blob.
- 0xjnml 2y ago> This would be much harder to do with modernc. https://go.dev/play/p/IztwH9Jl68i https://go.dev/play/p/IztwH9Jl68i