[lucideer]

The wording & framing of these things is an interesting topic in the context of the W3C's decision to drop WebSQL.

A "rewrite" softly implies a replacement (intent that SQLite users would all migrate to Turso eventually & SQLite would cease to exist as a project). This isn't the strict definition of a rewrite but the implication is there in the language.

OTOH the W3C shut down that spec because it required competing implementations to exist. This imagines a world where Turso & SQLite coexist actively.

E.g. micropython isn't a rewrite of cpython even though they both target compatible python, Chrome isn't a rewrite of Firefox even though they both target a range of compatible languages & formats (but Firefox was a rewrite of Netscape - the word depends heavily on context).

I realise this usage isn't coming from you, it's coming from the Turso devs themselves, but it does feel like an overstep on their part.

The Turso guys can use whatever words they like in their blogposts, they're not the authority on whether it constitutes a rewrite.

[egorfine]

> it does feel like an overstep on their part.

It's the Rust superiority complex that's subtly speaking thru the Rust "rewrite" projects. Of course rust is better so why would anyone want to stay on the old, C-coded version?