1. Rust rewrite – performance, safety, and concurrency
“They’re implementing MVCC” – maxmcd
“Concurrent writes already working is a reasonable definition of success.” – fragmede
The discussion centers on whether Rust can deliver the same speed and reliability as C while adding features like MVCC and concurrent writes.
2. Test‑suite reliability and the SQLite “black‑box”
“SQLite’s test suite is infamously gigantic… the public tests are tiny compared to what SQLite actually runs internally.” – adamzwasserman
“The full SQLite test suite isn’t open source, so you (the third party) don’t have the same confidence in your modifications as the SQLite team does.” – jzebedee
Users argue that without access to the proprietary tests, a rewrite risks missing subtle bugs that the original SQLite team catches.
3. VC‑backed startup vs. open‑source sustainability
“I can easily see how SQLite’s development is sustainable, but not Turso’s.” – ndiddy
“Free VC‑backed software always means ‘free… until it’s in our interest to charge for it’.” – CodingJeebus
Critics warn that Turso’s funding model could lead to a rug‑pull or a shift away from the open‑source ethos.
4. Compatibility and feature gaps with SQLite
“SQLite compatibility for SQL dialect, file formats, and the C API.” – IshKebab
“The sqlite API isn’t fully implemented yet, so I wrote a declarative facade that backfills the missing implementations.” – adamzwasserman
The conversation highlights the tension between maintaining strict compatibility and adding new features that SQLite doesn’t yet support.