HN Explorer

9 comments

[ 4.0 ms ] story [ 27.1 ms ] thread
pstuart
So is this a handmade port vs the translated port done by modernc?
spwa4
It's machine translated with TLA, tested, and finished by adding a few extra pure go mechanisms (such as Go code-backed virtual tables)
yodon
Seems like there are some trademark issues with just calling this SQLite.
jsherer
I was confused a few weeks ago. Check out the go pkg: https://pkg.go.dev/modernc.org/sqlite

1. gitlab.com/cznic/sqlite is the primary repo

2. github.com/cznic/sqlite was the github mirror but it moved

3. github.com/mordernc-org/sqlite is the read-only mirror of the primary repo

Cheers!

[dead] ftgffsdddr
[flagged]
qweqwe14
Just use a real web browser or enable JS, it's not that hard buddy. "Why do you keep hitting yourself?"
usrnm
The readme really lacks the answer to the "why" question. What's the use case, why should I prefer it over real sqlite?
ncruces
There's also my take on this [1], which does machine translation from C to Go via Wasm using [2].

It's a somewhat less faithful translation, since I manually ported the VFS (SQLite OS abstraction layer).

OTOH, each SQLite connection is sandboxed (can't access/corrupt Go memory, or other SQLite connections). And it should run everywhere Go runs.

1: https://github.com/ncruces/go-sqlite3

2: https://github.com/ncruces/wasm2go

pjjpo
This project seems to get shared every month or so. It's really sad that HN's signal to noise has fallen this hard... While I continue to have it in my feed, I'm more and more opening up Reddit since it just feels more robust now adays.