well they're in the best/only(?) spot to do it -- owning the platform the end-programmer code is running on. SQLite is well built and extensible but hard to extend without the cooperation of the end-programmer, so to speak.
SQLite is unfortunately (?) kind of hard to modify for external processes and while it's built very extensibly it's often not the thing you can kind of just... turn on, if that makes sense, and SQLite lives in the address space of the executing program.
You end up with stuff like hacking LD_PRELOAD[0].
Note: Litestream (Ben) was acquihired essentially by Fly.io (so that should explain all their recent SQLite content!).
SQLite is unfortunately (?) kind of hard to modify for external processes and while it's built very extensibly it's often not the thing you can kind of just... turn on, if that makes sense, and SQLite lives in the address space of the executing program.
You end up with stuff like hacking LD_PRELOAD[0].
Note: Litestream (Ben) was acquihired essentially by Fly.io (so that should explain all their recent SQLite content!).
[0]: https://github.com/cventers/sqlite3-preload