s6 VS go-sqlite

A (rare) good critique to systemd can be found here. Written by the developer behind s6, which happens to be scheduled to replace OpenRC on Alpine Linux. For completeness-sake, some of the main reasons why Alpine doesn't prefer systemd do not apply on most other distros.

It got mass-adopted while being imperfect, so that's to be expected. Thankfully its inception and the criticism that followed have paved the way for the likes of dinit and s6.

this page and this page, both by Laurent Bercot, creator of s6.

Of the two I have experience with, runit is simpler and thus easier to get the hang of than s6-rc/s6. Though the s6 (not s6-rc) docs at the author's site contain a lot of info (including apologetics and rationales) that applies almost equally well to runit

systemd: Yes; it's awaiting its "PipeWire". Thankfully, the likes of s6 and dinit are very promising. Though I can actually appreciate that systemd is addressed. As ultimately it helps in raising awareness that will benefit whatever software will replace it eventually.

Arguably this is less troublesome to solve compared to the other concerns. As we're inevitably waiting for the system supervision suite that will be to systemd what PipeWire has been to PulseAudio. I'm very optimistic about this as both s6 and Dinit are shaping up lovely.

Using the s6-service add command I added a service called "libvertd" when I ment to put "libvirtd". Now when I run s6-db-reload it spits out a error message saying "undefined service name libvertd". But I cant remove it using s6-service remove libvertd because that just spits out a generic help message and doesn't change anything. I also couldn't find documentation on https://skarnet.org/software/s6/ or https://skarnet.org/software/s6-rc/ as the command just *doesn't* exist on those pages. (also no man or info page).

Check out https://github.com/zombiezen/go-sqlite if you're interested in trying out Sqlite in Go again. Nice interface, negligible compile time impact, fast, compiles without CGO. It's very comfortable.

I agree that going from text to sqlite is a bit of a hurdle, especially if you're not writing C :)

struggling figuring out how to make my cgo sqlite cross-compile to Windows

Plenty of people trying to fix that.

There's at least:

https://modernc.org/sqlite

Then there's https://github.com/zombiezen/go-sqlite that actually builds https://crawshaw.io/sqlite on top of modernc.

And there's mine that has both a low level and a database/sql driver builds and runs everywhere Go does: https://github.com/ncruces/go-sqlite3

There are several different Go bindings for SQLite. I maintain https://pkg.go.dev/zombiezen.com/go/sqlite

I like and use https://github.com/zombiezen/go-sqlite for CGo-free SQLite. It avoids some of the problems database/sql has, discussed here: https://crawshaw.io/blog/go-and-sqlite.

> C libraries are required to interact with SQLite

Or: modernc.org/sqlite (https://github.com/zombiezen/go-sqlite), "an automatically generated translation of the original C source code of SQLite into Go"

https://pkg.go.dev/modernc.org/sqlite via https://pkg.go.dev/zombiezen.com/go/sqlite

modernc.org/sqlite provides a database/sql driver, but does not (currently) provide an easy way to get at the more advanced functionality of SQLite, like streaming blob I/O or user-defined functions. David Crawshaw has argued that the database/sql API is not a good fit for SQLite, which is how crawshaw.io/sqlite came about.