Upvoted. SQLITE as an API does so many things right:
- Providing it's own malloc/free "proxies" to work away with different linked CRT versions (Microsoft) - Prefixing ("namespacing") everything, and not exporting symbols outside of the API - Configuration of the API before it's started, where it makes sense (threading model for example) - Ability to retrieve compilation options back (e.g. how it was compiled and with what features) - many other things
Agree with you on the importance of backwards compatibility. But there is also the idea that you should at some point draw the line and break compabitibility so that you can really fix things is also defendable. In my opinion by releasing the library/project under a new name, like python does.
The worst and most common though is the "break all things for no reason at all"...
sqlite4 OTOH seems to be the "let's break things" phase. Probably healthy to have both attitudes at certain stages.