Limbo: A complete rewrite of SQLite in Rust
1–10 of 238 posts
Re: Limbo: A complete rewrite of SQLite in Rust
#2Dunno. Good luck to them, but I never saw a need to rewrite sqlite.
Re: Limbo: A complete rewrite of SQLite in Rust
#3Dunno. Good luck to them, but I never saw a need to rewrite sqlite.
Guessing the shortcomings become starker if you’re spending lots of time in the codebase/building a company on top of it.
Re: Limbo: A complete rewrite of SQLite in Rust
#4Dunno. Good luck to them, but I never saw a need to rewrite sqlite.
Guessing the shortcomings become starker if you’re spending lots of time in the codebase/building a company on top of it.
Yeah… Attempting to integrate MVCC and then doing vector search gave enough perspective to do this!
Re: Limbo: A complete rewrite of SQLite in Rust
#5I’ll take the faster c version anyday over the rust. How are those conditional if statements working for you all?
Re: Limbo: A complete rewrite of SQLite in Rust
#6I am not sure how feasible it is, but can't SQLite be partially rewritten step by step on the main branch instead of being forked?
As the article mentioned, a complete rewrite will not be as stable as the original.
Re: Limbo: A complete rewrite of SQLite in Rust
#7I’ll take the faster c version anyday over the rust. How are those conditional if statements working for you all?
The benchmarks in the post indicate that Limbo is more performant than SQLite, not less.
Re: Limbo: A complete rewrite of SQLite in Rust
#8disclosure: I work here. I am happy to answer any questions
tl;dr We are rewriting SQLite in Rust. It uses Asynchronous I/O, considers WASM as first class, and has Deterministic Simulation Testing support from the beginning.
Re: Limbo: A complete rewrite of SQLite in Rust
#9When the initial SQLite3->LibSQL fork was announced I was pretty negative about it because SQLite3 has a wonderful, 100% branch coverage test suite that is proprietary, and so without access to that any fork would be bound to fail.
However, if there's a big product behind the fork, and even better, a rewrite to a memory-safe language, then the fork begins to make a lot of sense. So, hats off to y'all for pulling this off!
Re: Limbo: A complete rewrite of SQLite in Rust
#10I am not sure how feasible it is, but can't SQLite be partially rewritten step by step on the main branch instead of being forked? As the article mentioned, a complete rewrite will not be as stable as the original.
> can't SQLite be partially rewritten step by step on the main branch
Only by the SQLite team. They don't accept contributions of anything other than spelling fixes and such.