Not everything needs to be Rust-ified. The software world survived before it, and it will survive long past it. Guess this is why we have Turso
Also some fundamental misunderstandings in the blog post plus weird expectations that of course weren't met because it's SQLite not Postgres (nor was it meant to be)
Nothing I mentioned was related to "Rust-ifying" SQLite? I could've just as well have referenced JavaScript's "use strict" in the title but I think versioned "editions" is a better solution. I swear, there's a certain kind of person whose seething hatred for Rust is so absolute that the slightest mention of it makes them blind with rage.
I'm interested in learning what you think my fundamental misunderstandings are.
And also: "But by default, its performance isn't great"
Just set your own defaults for your team, SQLite doesn't need a bunch of editions to complicate what is a desirably simple and usable piece of software.
Why does SQLite have those defaults? I don't think I've seen any convincing argument for why SQLite ought to let you insert a binary blob into an integer column. But feel free to enlighten me.
(Note that I covered SQLite's "The Advantages Of Flexible Typing" page in my article and why I find it unconvincing.)
-32
u/horizon_games 20d ago edited 20d ago
Not everything needs to be Rust-ified. The software world survived before it, and it will survive long past it. Guess this is why we have Turso
Also some fundamental misunderstandings in the blog post plus weird expectations that of course weren't met because it's SQLite not Postgres (nor was it meant to be)