groundzeros2015 13 hours ago

Without the test suite isn’t even more likely to have stability problems?

dlisboa 12 hours ago | parent | next [-]

Maybe. It's hard to know what kind of issues that test suite covers. If memory safety is the main source of instability for the C implementation then the Rust implementation won't be too affected without the test suite. Same if it focus a lot on compatibility with niche embedded platforms and different OSes, which Turso won't care to lose.

"Stability" is a word that means different things for different use cases.

	▲	groundzeros2015 12 hours ago \| parent [-]
		Coverage is described on the SQLite website

▲

0x457 13 hours ago | parent | prev | next [-]

Turso has its own test suite that in the repo.

▲

groundzeros2015 13 hours ago | parent [-]

but the other one has decades of engineering effort and is based on real world problems

	▲	0x457 6 hours ago \| parent [-]
		But the other one is not available to most and SQLite itself is "open-source" not "open-contributions" so extending SQLite is pretty much impossible at scale: - no way to merge upstream - no way to run full test-suit to be sure everything is tiptop

▲

9rx 12 hours ago | parent | prev [-]

Not likely. The alternative was for them to modify SQLite without the test suite and no obvious indication of what they would need to do to try to fill in the gaps. Modifying SQLite with its full test suite would be the best choice, of course, but one that is apparently[1] not on the table for them. Since they have to reimagine the test suite either way, they believe they can do a better job if the tests are written alongside a new codebase.

And I expect they are right. Trying to test a codebase after the fact never goes well.

[1] With the kind of investment backing they have you'd think they'd be able to reach some kind of licensing deal, but who knows.