3 ms·
It's too bad and honestly kinda a bummer how all this panned out. Mozilla people pushed really hard against "just use sqlite" because it's not a spec, and comp
by coleifer 7y ago
It's too bad and honestly kinda a bummer how all this panned out.
Mozilla people pushed really hard against "just use sqlite" because it's not a spec, and compatible alternatives would need to implement some of the quirks of sqlite. Unfortunately, nothing as good as sqlite has ever materialized, but this argument essentially blocked websql from becoming "officially blessed" by the w3c.
Around this time Mozilla was also was drinking the koolaid hard and somehow we ended up with something literally nobody wanted: indexeddb. There's a funny article which is made even better by it's earnest, unironic use of the term "aesthetics" to describe indexeddb [1].
Another tragic instance of design-by-committee and a complete lack of pragmatism.
[1] https://hacks.mozilla.org/2010/06/beyond-html5-database-apis-and-the-road-to-indexeddb/ https://hacks.mozilla.org/2010/06/beyond-html5-database-apis...
- nine_k 7y agoNo two independent implementations -> not standard-worthy :( I would love to see an SQL interface in the browser. I suppose it's going to be a library on top of indexed DB, and / or a WASM implementation. Then it would have a chance to become a standard.