This is going to get confusing if it's not a Go implementation of SQLite. But it seems there's some relation to it since there's a #include <sqlite3.h> in the main.c. Would be great if the README could elaborate a bit on that.
Refreshing read. A lot of these posts people tend to try to justify their decision mostly after-the-fact based on usually very poor data or just some opinions/expectations. The author however completely acknowledges that their reason for doing so was just because they wanted to have some fun, and got some benefits out of it too.
The LOC change is fairly dramatic but it does make me wonder how much potential dead code was in the old codebase. Especially if it's been around for a while it'll likely have accumulated baggage that the newly implemented version just doesn't have.
I'm sure this is a perfectly fine mux but I'm a bit puzzled as to why Go developers seem to constantly want to invent their own server mux. There's at least 10 I can think of, most with overlapping feature sets.
Though it's definitely interesting to do this as an exercise to also understand how this is all wired together in Go, I do wonder why people expense effort in writing, or at least maintaining, their own over leveraging and contributing to an existing one, like (fast)httprouter, Chi, Gorilla Mux? Just about every other one is implemented as a (radix) tree too.