Hacker News Reader

Seems like a distinction without a difference to rewrite "sqlite in c" to "not sqlite but sqlite-like in rust or go".

How is it not different? It would be a completely new library. I don't see what the argument against that is.

You're free to do so, as is anyone.

But you'll have to overcome and provide a good reason for why anyone using sqlite should move to your new unproven shiny.

If anything sqlite is a poster child for c done (and tested/validated) right. You'll have to demonstrate a lot more than you can implement some things better in the new language.

I'm going to stop here since the goalposts keep moving. My point is: no one brought "rewrite in rust" up but yourself.

Fair enough, but I guess I don't see a difference between rewrite sqlite in rust and, make something exactly like sqlite, with a c ffi but in rust.

I interpreted that commentary as referencing a new library similar in architecture, like an implementation of S3 that lives locally in the software and is modeled after SQLite. Not “let’s rewrite SQLite” like everyone else seems to have run with.

Reply on news.ycombinator.com