Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Deep dive into Turso, the “SQLite rewrite in Rust”

kerkour.com

Post reply on HN
Print view View original

21–30 of 154 posts

Re: Deep dive into Turso, the “SQLite rewrite in Rust”

#21

Post by jancsika »

sauercrowd wrote: post #13

> ... most of which can be fixed by a rewrite in Rust huh? That is clearly not the case. memory bugs - sure. Not having a public test suite, not accepting public contributions, weakly typed columns and lack of concurrency has nothing to do with the language. They're governance decisions, that's it. >I see this situation trhough the prism of the innovator's dilemma: the incumbent is not willing to sacrifice a part of…

> lack of concurrency has nothing to do with the language

That's an extraordinary claim for any C codebase.

Unless it ships with code enabling concurrency that is commented out, we should assume that "concurrency in C ain't easy" was a factor in that design choice.

Re: Deep dive into Turso, the “SQLite rewrite in Rust”

#22

Post by ndiddy »

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 about how they're going to get 100x returns I'm not sure how long that'll last. VCs generally expect companies they invest in to grow to $100 million in revenue in 5-10 years. If your use of their technology doesn't help them get there, you should expect to be rugpulled at some point.

Re: Deep dive into Turso, the “SQLite rewrite in Rust”

#24

Post by gus_massa »

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?)

Re: Deep dive into Turso, the “SQLite rewrite in Rust”

#25

Post by floren »

rantingdemon wrote: post #23

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.

Re: Deep dive into Turso, the “SQLite rewrite in Rust”

#26

Post by duped »

roywiggins wrote: post #6
causalscience wrote: post #3

Earlier quoted context omitted.

[flagged]

pglite runs in wasm so it should be possible to embed it where you want, like sqlite?

Why would I want wasm for an embedded database? It's not a feature, quite an anti-feature frankly.

edit: it looks like pglite is only useful for web apps

Re: Deep dive into Turso, the “SQLite rewrite in Rust”

#27

Post by CodingJeebus »

ndiddy wrote: post #22

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…

Completely agree, I'm looking at pretty much all software this way nowadays.

We've all been around long enough to know that "free" VC-backed software always means "free... until it's in our interest to charge for it". And yet users will still complain about the rugpull in 2026, no matter how many times they've been through it. "Fool me once, shame on you"

Re: Deep dive into Turso, the “SQLite rewrite in Rust”

#29

Post by fulafel »

Havoc wrote: post #18

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

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

Post reply on HN