4 ms·
Yeah, me too. I think it's just politics, in the best traditions of big corporations, that doesn't do any good to actual web developers. From practical perspec
by k7d 16y ago
Yeah, me too. I think it's just politics, in the best traditions of big corporations, that doesn't do any good to actual web developers.
From practical perspective we would be better off with Web SQL DB. Functionally it addresses everything a developer needs to create offline HTML apps. API is not perfect but you can always improve that with small wrapper libraries (like JQuery improves DOM API). You can always easily implement IndexDB-like API on top off SQL if you really want that. The opposite is probably possible but much more difficult.
Also I think IndexDB might turn out to be yet another compatibility headache because everybody will be creating their own implementation (I'm pretty sure there will be at least 3 - Microsoft, Mozilla & Webkit). It's a speculation but most likely this wouldn't be an issue with Web SQL DB because everybody would just use the same SQLLite backend.
And worst of all, this is delaying progress of web applications. Lack of solid cross-browser client-side storage solution is the last big gap for next generation of web applications. If everybody had just agreed on SQLLite we could be there today... now it's still unknown when we will get there.
- sid0 16y agoAlso I think IndexDB might turn out to be yet another compatibility headache because everybody will be creating their own implementation (I'm pretty sure there will be at least 3 - Microsoft, Mozilla & Webkit). It's a speculation but most likely this wouldn't be an issue with Web SQL DB because everybody would just use the same SQLLite backend. For a proposed web standard to become an actual web standard there need to be at least two implementations. This is a good, healthy thing. There was going to be no second implementation of Web SQL, so it was never going to become a standard.