Thanks to a few very small people, WebSQL was deprecated before it had a chance to prove anything.
There was (and still is) no independent implementation of SQLite that was battle-tested even a bit.
It was not proven at all. WebSQL was deprecated based on "we don't want to standarize on single project". IndexedDB happened because they wanted to standarize on single API (lmao), but it was just too inept.
There is no one size fits all but WebSQL fit A LOT of use cases.
Low level storage that works for DBs is interesting idea but that also means you need to ship additional megabytes of code with every app.
Also, couldn't the implementation of that storage spec. be shipped in the standard JS web APIs (i.e. by the browser)? Why would it be in every app?
> Also, couldn't the implementation of that storage spec. be shipped in the standard JS web APIs (i.e. by the browser)? Why would it be in every app?
Actually, that is exactly what happens to WebSQL and IndexedDB. WebSQL got deprecated, they were not able integrate SQLite, and created IndexedDB, which is hated by many developers. Just an example: https://news.ycombinator.com/item?id=27511941
The Origin Privet File System api is going to provide the opportunity for any db engine to be used in offline first PWAs.
There is no “one size fits all” database engine, that was proved by both WebSQL and IndexedDB. The OPFS in combination with WASM is the correct solution to in browser DBs.