IMHO breaking free of SQLite's proprietary test suite is a bigger driver than C vs Rust. Turso's Limbo announcement says exactly that: they couldn't confidently make large architectural changes without access to the tests. The rewrite lets them build Deterministic Simulation Testing from scratch, which they argue can exceed SQLite's reliability by simulating unlikely scenarios and reproducing failures deterministically.

▲

pseudohadamard 29 minutes ago | parent | next [-]

Having seen way too many "we're going to rewrite $xyz but make it BETTERER!!", I don't give this one much chance of success. SQLite is a high-quality product with a quarter-century of development history and huge amounts of effort, both by the devs and via pubic use, of testing. So this let's-reinvent-it-in-Rust effort will have to beat an already very good product that's had a staggering amount of development effort and testing put into it which, if the devs to manage to get through it all, will end up being about the same as the existing thing but written in a language that most of the SQLite targets don't work with.

▲

CharlesW 12 hours ago | parent | prev [-]

> IMHO breaking free of SQLite's proprietary test suite is a bigger driver than C vs Rust.

I don't understand this claim, given the breadth and depth of SQLite's public domain TCL Tests. Can someone explain to me how this isn't pure FUD?

"There are 51445 distinct test cases, but many of the test cases are parameterized and run multiple times (with different parameters) so that on a full test run millions of separate tests are performed." - https://sqlite.org/testing.html

▲

lmm 5 hours ago | parent | next [-]

The test suite that the actual SQLite developers use to develop SQLite is not open-source. 51445 open-source test cases is a big number but doesn't really mean much, particularly given that evidently the SQLite developers themselves don't consider it enough to provide adequate coverage.

▲

einsteinx2 11 hours ago | parent | prev | next [-]

The irony is if they only had the public domain tests, no one would complain even though it would mean the exact same number of open source tests.

	▲	dullcrisp 14 minutes ago \| parent [-]
		That’s like if I gave you half the dictionary and then said it’s ironic that if there really weren’t any letters after “M” you wouldn’t be complaining.

▲

Ar-Curunir 3 hours ago | parent | prev | next [-]

There are also non-public tests.

▲

digitalPhonix 11 hours ago | parent | prev [-]

The next bullet point:

> 2. The TH3 test harness is a set of proprietary tests…

▲

CharlesW 11 hours ago | parent [-]

Of course, but how does that make the allegation not FUD?

	▲	digitalPhonix 7 hours ago \| parent [-]
		I’m confused, the statement is that SQLite has a proprietary test suite? It does. Where’s the FUD? Turso tried to add features to SQLite in libsqlite but there were bugs/divergent behaviour that they couldn’t reconcile without the full test suite.