61–70 of 154 posts
I’d imagine this will go a bit like the rust rewrite of sudo etc. Despite the memory safety advantages at least towards the start it still ends up more fragile because the incumbent has years of testing and fixing behind it
Isn’t the rust rewrite deployed as part of some fairly significant Linux distros these days? That’s hearsay that I haven’t dug into, so I may well be wrong.
The thing that worries me the most about Turso is that rather than the small, stable team running SQLite, Turso is a VC backed startup trying to capitalize on the AI boom. I can easily see how SQLite's development is sustainable, but not Turso's. They're currently trying to grow their userbase as quickly as possible with their free open source offering, but when they have investors breathing down their necks asking a…
I too am weary of VC incentives but: 1) It's MIT licensed. Including the test suite which is something lacking in SQLite: https://github.com/tursodatabase/turso 2) They have a paid cloud option to drive income from: https://turso.tech/pricing
You must be kidding. Last time I checked, sqlite was mostly extensive test suites.
Earlier quoted context omitted.
They're not aiming at replacing SQLite-in-C with SQLite-in-Rust, they're doing this so they can implement more additional functionality faster than with C's chainsaw-juggling-act semantics and the inability to access the proprietary SQLite test suite. See the features and roadmap at https://github.com/tursodatabase/turso
Without the test suite isn’t even more likely to have stability problems?
"Stability" is a word that means different things for different use cases.
Earlier quoted context omitted.
I too am weary of VC incentives but: 1) It's MIT licensed. Including the test suite which is something lacking in SQLite: https://github.com/tursodatabase/turso 2) They have a paid cloud option to drive income from: https://turso.tech/pricing
> test suite which is something lacking in SQLite You must be kidding. Last time I checked, sqlite was mostly extensive test suites.
Earlier quoted context omitted.
They're not aiming at replacing SQLite-in-C with SQLite-in-Rust, they're doing this so they can implement more additional functionality faster than with C's chainsaw-juggling-act semantics and the inability to access the proprietary SQLite test suite. See the features and roadmap at https://github.com/tursodatabase/turso
In other words, they are creating their own database and hitching on to the SQLite brand to market it. (That's fine though).
Building off of that into a SQLite-compatible DB doesn't seem to me as trying to piggyback on the brand. They have no other option as their product was SQLite to begin with.
Earlier quoted context omitted.
I too am weary of VC incentives but: 1) It's MIT licensed. Including the test suite which is something lacking in SQLite: https://github.com/tursodatabase/turso 2) They have a paid cloud option to drive income from: https://turso.tech/pricing
> test suite which is something lacking in SQLite You must be kidding. Last time I checked, sqlite was mostly extensive test suites.
This is very shallow for a supposed deep dive. I'm not ready to entertain Turso as an alternative to something that is as battle tested as Sqlite.
> This is very shallow for a supposed deep dive. I think it's time for a new law of headlines: anything labeled a "deep dive" isn't.
I was surprised that the test suit not open source. Some info in https://sqlite.org/testing.html It looks like some parts are open source and other not. Does anyone know more about the backstory? (It looks like one is a custom program that generate fuzz test. Do they sell it to others SQL engines?)
Earlier quoted context omitted.
I too am weary of VC incentives but: 1) It's MIT licensed. Including the test suite which is something lacking in SQLite: https://github.com/tursodatabase/turso 2) They have a paid cloud option to drive income from: https://turso.tech/pricing
> 2) They have a paid cloud option to drive income from: I’ve been confused by this for a while. What is it competing with? Surely not SQLite, being client server defeats all the latency benefits. I feel it would be considered as an alternative to cloud Postgres offerings, and it seems unlikely they could compete on features. Genuinely curious, but is there any sensible use case for this product, or do they just catc…