Why would you rewrite something that’s widely considered one of the best written and tested pieces of software in the world?
Also, they're building a project that's more open to outsiders.
Turso has a booming OSS community with many contributors from outside the company and is fully MIT.
It’s fast, with unparalleled stability, arguably better managed than any other software on earth, deployed on literally everything, so let’s… fork it for street cred?
But with LLMs and massive, human-written test suites, rewrites aren’t a bad idea like they used to be. Rust is a perfect target language because it’s compiler is so strict and surfaces issues in a way that’s easy for either humans or LLMs to use.
Even if they weren’t, LLMs are pretty good at writing tests because of Github being in their training sets. I rarely find that their tests are bad unless I underspecified what the project is supposed to do.
Disclaimer that I only vibe-code for personal projects, so I haven’t tested this at business scale.
Sqlite is excellent but I still have many gripes with it, especially around defaults.
54min in was what I was thinking of.
“Lots of people have tried, you’re welcome to try”
I apologize if I gave a bad gloss, but I think it was roughly in the spirit of what you said.
Q: If a young developer said they wanted to fork SQLite and build something better, what would you tell them?
A: ... lots of people have tried. You're welcome to try. I think that the time has passed; it takes twenty five years, and it takes maniacal devotion to the cause.
That's basically the opposite of any other project where you pay to get support and a certified official build of the exact same code as open source releases, and if there's a private part it's paperwork you can show as proof of compliance for safety critical systems.