SQLite Codebase Quality

Does it being written by the Sqlite devs not improve the outlook for you?

Agreed, its not a vanilla SQLite but can give you a rough idea of the quality of SQLite codebase.

SQLite is the one project that deserves an exception. There is a near zero chance anyone else can do better with similar quality (and test coverage!)Sometimes you need to be pragmatic IMHO.

Seems like entirely self inflicted problem; SQLite is not closed source, it doesn't need independent implementations

SQLite is so extensively tested and widely used it may as well be written in stone. It doesn't count as "writing C".

sqlite's test suite is substantial and not open source, I doubt you could really fork it in a meaningful way

SITUATION: there are too many competing SQLite forks...

By all means, fork the code base for your specific use case, but I'll trust drh and his team over some rando any day.sqlite isn't the most widely used database by accident - it's installed on practically every mobile phone on earth. It's the result of careful and deliberate design with millions of tests and fuzzing. The sqlite team is very responsive to its users' needs, but some features just don't make the cut. That's a good thing - to keep the library

Wouldn't that be leaving one huge advantage of sqlite behind (namely it's insane test regimen and battle tested history)?

Read SQLite's FAQ on that. Given, most projects aren't as amazing as SQLite.