News for hackers. Stuff that matters.
Re:Why Is SQLite Coded in C and not Rust by slashdev on Tuesday October 14, 2025 @07:51PM (#45586376)
This is ignoring the elephant in the room: SQLite is being rewritten in Rust and it's going quite well. https://github.com/tursodatabase/turso

It has async I/O support on Linux with io_uring, vector support, BEGIN CONCURRENT for improved write throughput using multi-version concurrency control (MVCC), Encryption at rest, incremental computation using DBSP for incremental view maintenance and query subscriptions.

Time will tell, but this may well be the future of SQLite.

Re:Why Is SQLite Coded in C and not Rust by assimpleaspossi on Tuesday October 14, 2025 @08:03PM (#45586449)
>>SQLite is being rewritten in Rust

SQLite is NOT being rewritten in Rust!

>>Turso Database is an in-process SQL database written in Rust, compatible with SQLite.

Re:Why Is SQLite Coded in C and not Rust by slashdev on Tuesday October 14, 2025 @09:12PM (#45586972)
It's a ground up rewrite. It's not an official rewrite, if that's what you mean. Words are hard.
Re:Why Is SQLite Coded in C and not Rust by stoltzmann on Wednesday October 15, 2025 @03:00AM (#45588945)
So a reimplementation, not a rewrite.
Re:Why Is SQLite Coded in C and not Rust by slashdev on Wednesday October 15, 2025 @04:04PM (#45597708)
That's a better word, thank you
Re:Why Is SQLite Coded in C and not Rust by saghm on Friday October 17, 2025 @03:04PM (#45620663)
How does one implement software other than writing it?
Re:Why Is SQLite Coded in C and not Rust by blibble on Tuesday October 14, 2025 @08:10PM (#45586506)
> Time will tell, but this may well be the future of SQLite.

turdso is VC funded so will probably be defunct in 2 years

Re:Why Is SQLite Coded in C and not Rust by daxfohl on Tuesday October 14, 2025 @08:22PM (#45586601)
Or, so it's being written mostly by AI.
Re:Why Is SQLite Coded in C and not Rust by slashdev on Tuesday October 14, 2025 @09:17PM (#45587013)
Could also be an outcome. It is MIT open-source though.
Re:Why Is SQLite Coded in C and not Rust by zvmaz on Tuesday October 14, 2025 @07:54PM (#45586396)
In the link you provided, this is what I read: "An in-process SQL database, compatible with SQLite."

Compatible with SQLite. So it's another database?

Re:Why Is SQLite Coded in C and not Rust by simonw on Tuesday October 14, 2025 @07:57PM (#45586422)
Yeah, I don't think it even counts as a fork - it's a ground-up re-implementation which is already adding features that go beyond the original.
Re:Why Is SQLite Coded in C and not Rust by ForHackernews on Wednesday October 15, 2025 @04:18AM (#45589501)
It's a fork and a rewrite.
Re:Why Is SQLite Coded in C and not Rust by lionkor on Tuesday October 14, 2025 @08:06PM (#45586479)
So they have much worse test coverage than sqlite
Re:Why Is SQLite Coded in C and not Rust by metaltyphoon on Tuesday October 14, 2025 @07:55PM (#45586406)
The moment turso becomes stable , SQLite will inevitably fade away with time if they don’t rethink how contributions should be taken. I honestly believe the Linux philosophy of software development will be what catapults turso forward.
Re:Why Is SQLite Coded in C and not Rust by tonyhart7 on Tuesday October 14, 2025 @07:55PM (#45586403)
so its sqlite++ since they added bunch of things on top of that
Re:Why Is SQLite Coded in C and not Rust by 3eb7988a1663 on Tuesday October 14, 2025 @08:27PM (#45586640)
It should be noted that project has no affiliation with the SQLite project. They just use the name for promotional/aspirational purposes. Which feels incredibly icky.

Also, this is a VC backed project. Everyone has to eat, but I suspect that Turso will not go out of its way to offer a Public Domain offering or 50 year support in the way that SQLite has.

Re:Why Is SQLite Coded in C and not Rust by slashdev on Tuesday October 14, 2025 @09:15PM (#45586999)
> They just use the name for promotional/aspirational purposes. Which feels incredibly icky.

The aim is to be compatible with sqlite, and a drop-in replacement for it, so I think it's fair use.

> Also, this is a VC backed project. Everyone has to eat, but I suspect that Turso will not go out of its way to offer a Public Domain offering or 50 year support in the way that SQLite has.

It's MIT license open-source. And unlike sqlite, encourages outside contribution. For this reason, I think it can "win".

Re:Why Is SQLite Coded in C and not Rust by frumplestlatz on Wednesday October 15, 2025 @03:13AM (#45589035)
Calling it “SQLite-compatible” would be one thing. That’s not what they do. They describe it as “the evolution of SQLite”.

It’s absolutely inappropriate and appropriative.

They’ve been poor community members from the start when they publicized their one-sided spat with SQLite over their contribution policy.

The reality is that they are a VC-funded company focused on the “edge database” hypetrain that’s already dying out as it becomes clear that CAP theorem isn’t something you can just pretend doesn’t exist.

It’ll very likely be dead in a few years, but even if it’s not, a VC-funded project isn’t a replacement for SQLite. It would take incredibly unique advantages to shift literally the entire world away from SQLite.

It’s a new thing, not the next evolution of SQLite.

Re:Why Is SQLite Coded in C and not Rust by slashdev on Wednesday October 15, 2025 @04:04PM (#45597701)
The founders came from ScyllaDb, I wouldn't be so quick to count them out. The repo has a lot of contributors and traction. As long as the company survives, I think it has a bright future.
Re:Why Is SQLite Coded in C and not Rust by frumplestlatz on Wednesday October 15, 2025 @06:43PM (#45599223)
So they have a history of using the legitimacy, trust, and infrastructure of the open-source ecosystem to grow adoption and contributions, then gradually shifting constraints in favor of monetization and control?

Either way, the math is different this time. SQLite isn’t heavy server-side software written in Java with weaknesses that leave it obviously open for market disruption.

It’s also a public domain gift to the world that literally everything has deployed — often in extremely demanding and complex environments.

I work for a major consumer product manufacturer, and I can guarantee that we will not be switching away from SQLite anytime soon, and if we ever do, it will not be to a VC-backed project with a history like this one has, no matter how much hype startup bros try to create around the idea of disrespectful and appropriative disruption.

VC-funded ‘open’ databases almost always follow the same arc: borrow legitimacy, capture attention, then fence it off. It’s the inevitability of the incentives they’ve chosen.

Re:Why Is SQLite Coded in C and not Rust by penberg on Friday October 17, 2025 @03:04AM (#45614023)
You're not wrong about VC-funded database arc, but what history are you even talking about?

I am sure you understand that I have absolutely nothing to do with Scylla's licensing. I have not worked there for four years nor was I ever in a position there that I would even had that opportunity to influence such decisions.

I am also sure you understand that Scylla's development model was completely different: they had AGPL license and contributors had to sign a CLA, which is why they were able to relicense in the first place. Turso is MIT licensed and there's no barrier to contributing and, therefore, already a much bigger contributor base.

I fully understand the scepticism, but you're mistaken about the open source history of Turso's founders.

Re:Why Is SQLite Coded in C and not Rust by penberg on Friday October 17, 2025 @02:47AM (#45613948)
The project is MIT licensed with a growing community of contributors. It does not even matter how long the company lives, all that matters is that some of the core contributors live.
Re:Why Is SQLite Coded in C and not Rust by penberg on Friday October 17, 2025 @02:44AM (#45613928)
The actual reality is that I personally started the project because its synchronous architecture is holding back performance. You can read all about it in https://penberg.org/papers/penberg-edgesys24.pdf. The design is literally the next evolution of SQLite's architecture.
Re:Why Is SQLite Coded in C and not Rust by blibble on Wednesday October 15, 2025 @06:17AM (#45590289)
> The aim is to be compatible with sqlite, and a drop-in replacement for it, so I think it's fair use.

try marketing your burger company as "The Next Evolution of McDonalds" and see what happens

Re:Why Is SQLite Coded in C and not Rust by saghm on Friday October 17, 2025 @03:02PM (#45620636)
This might be a compelling argument if McDonalds were the name of a public domain project rather than a trademarked corporation
Re:Why Is SQLite Coded in C and not Rust by matinsjoe54 on Friday October 17, 2025 @03:02PM (#45620642)
Hire an Expert Hacker To Recover Your Lost Ethereum And Crypto Wallet/HIRE OPTIMUM HACKERS RECOVERY I Would Like To Take This opportunity To Express My Gratitude To OPTIMUM HACKERS RECOVERY For Using Their Hacking Expertise To Return My Stolen Cryptocurrency, Which Was Valued At $450,000. I Tried It And Was Sceptical, Optimum Hackers Recovery Helped Me And It Worked. I Got My Money Back. I’m Pleased I Found Them Early Since I Feared Never Get My Money Back From Those Fraudulent Internet Investments. Now I Am Grateful To Thier Service Rendering. You Can Also Reach Them On Email: [email protected] WhatsApp: + 1-256-256-8636 Website: https://optimumhackersrecovery.com
Re:Why Is SQLite Coded in C and not Rust by yrashk on Friday October 17, 2025 @09:42PM (#45624151)
This happened to FerretDB