SQLite works great in Fil-C with minimal changes. So, the argument for keeping SQLite written in C is that it gives the user the choice to either: - Build SQL

SQLite works great in Fil-C with minimal changes. So, the argument for keeping SQLite written in C is that it gives the user the choice to either: - Build SQLite with Yolo-C, in which case you get excellent performance and lots of tooling. And it's boring in the way that SQLite devs like. But it's not "safe" in the sense of memory safe languages. - Build SQLite with Fil-C, in which case you get worse (but still quite good) performance and memory safety that exceeds what you'd get with a Rust/Go/Java/whatever rewrite. Recompiling with Fil-C is safer than a rewrite into other memory safe languages because Fil-C is safe through all dependencies, including the syscall layer. Like, making a syscall in Rust means writing some unsafe code where you could screw up buffer sizes or whatnot, while making a syscall in Fil-C means going through the Fil-C runtime.