22 points | by tosh 6 hours ago ago
8 comments
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!
The readme really lacks the answer to the "why" question. What's the use case, why should I prefer it over real sqlite?
Seems like there are some trademark issues with just calling this SQLite.
SQL would have been SEQL if not for trademark issues, the torch is passed
Gitlab requires js
Would you please host it on a different forge, eg codeberg
Codeberg requires html
Would you please host it on a different forge that doesn't require a web browser?
So is this a handmade port vs the translated port done by modernc?
modernc is the name of the GitHub fork (identical repo) of the same project. This is machine translated, not hand written.
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!
The readme really lacks the answer to the "why" question. What's the use case, why should I prefer it over real sqlite?
Seems like there are some trademark issues with just calling this SQLite.
SQL would have been SEQL if not for trademark issues, the torch is passed
Gitlab requires js
Would you please host it on a different forge, eg codeberg
Codeberg requires html
Would you please host it on a different forge that doesn't require a web browser?
So is this a handmade port vs the translated port done by modernc?
modernc is the name of the GitHub fork (identical repo) of the same project. This is machine translated, not hand written.