Re:KV Storage, the Web's First Built-In Module
by benjaminjackman on Tuesday March 12, 2019 @08:19AM
(#19367402)
Maybe it will be possible to compile Sqlite to wasm and then using indexdb as a backing store for it. In which case perhaps a good enough polyfill would be accessible to Firefox.
Re:KV Storage, the Web's First Built-In Module
by virtualwhys on Tuesday March 12, 2019 @11:25PM
(#19375436)
The issue there is that each client/user has to download the wasm binary, unlike WebSQL where Sqlite comes bundled with the browser for free -- there are issues there as well, versioning/security, but not having to download anything is pretty nice, like the KV storage option, it's there to use immediately, no download, no parsing overhead.
Re:KV Storage, the Web's First Built-In Module
by bradleyjg on Tuesday March 12, 2019 @07:22AM
(#19367059)
Does anyone use non-mobile safari?
Re:KV Storage, the Web's First Built-In Module
by acdha on Tuesday March 12, 2019 @09:33AM
(#19367925)
On a fairly broad-interest site I just checked, Safari is the second most-popular browser behind Chrome. Even if you exclude iOS, which doesn't make sense for most sites, it's in the same range as either Internet Explorer or Edge.
Re:KV Storage, the Web's First Built-In Module
by scarface74 on Tuesday March 12, 2019 @09:20AM
(#19367815)
Yes and even though you haven’t owned a TV in 15 years,people still watch TV too....
Agreed, although having the implementation defined exclusively by Sqlite (which is why IndexedDB became the standard browser database) remains a rather large sticking point.
Aside from the standards group reverting the deprecation of WebSQL, Firefox adoption has dwindled to dangerous lows, and Microsoft now bases their browser on Chrome, so in the not too distant future one could simply target the dominant browsers, Chrome and Safari, and use WebSQL, deprecated or not (if in 10 years Chrome and Safari haven't removed WebSQL, when will they?).
Unlikely WebSQL will make a comeback though, frontend devs seem to like NoSQL-style structured data, which maps well to JavaScript object notation. Would be great to write the same relational SQL on server and client, but that's a pipe dream unless a drastic shift in standards committe direction happens.