I love Rust and I love SQLite, so you can guess. Iwas pretty excited when I lerned that "SQLite was rewritten in Rust" What is SQLite, actually? 2 things: a

Hacker News is a community-driven platform for sharing and discussing technology news, startups, and programming-related topics. Through user submissions and comments, Hacker News offers insights into emerging technology trends, industry developments, and entrepreneurial ventures. Readers can participate in discussions, share their insights, and stay informed about the latest advancements in technology and innovation.

Hacker News

Turso is a new database engine written in Rust that maintains compatibility with SQLite's file format while addressing long-standing limitations. It adds built-in encryption, MVCC with concurrent writes support, and async I/O with io_uring. Unlike SQLite, Turso can scale from in-process usage to networked deployment across multiple machines, making it suitable for projects that start small but may need to scale. The project supports extensions through a Rust SDK and aims to combine the simplicity of embedded databases with the scalability of traditional client-server databases.

Deep dive into Turso, the "SQLite rewrite in Rust"

... most of which can be fixed by a rewrite in Rust

An in-process database that can scale to multiple machines

I don’t think rust is holy enough to allow us rewrite the SQLite with it.

I don’t think Turso is trying to “replace” SQLite at all.
SQLite is incredibly battle-tested and its design trade-offs are very intentional.
Turso feels more like: “what if we keep SQLite’s simplicity and file format, but adapt it to modern needs like concurrency, encryption and distributed setups?”
C vs Rust here isn’t about holiness or ideology, it’s about different constraints and use cases.
If you need ultra-portability and decades of hardening, SQLite is unmatched.
If you need SQLite-like ergonomics but want to grow beyond single-process limitations, projects like Turso make sense.
Different tools, different problems.

I feel cringe when hearing something “rewrite in Rust”, bro think it’s better with Rust

Okay but this doesn’t address the biggest limitation which is the Rust is not portable in the same way that C is, this will never replace the core SQLite project because it’s throwing away the amount of testing and real world hardening the existing code base has on it’s logic for type safety instead. I’d personally have a logic hardened implementation than something memory safe in this case