5 ms·

Cool but we’ve had in browser databases since ages. Things like indexedDb and WebSql. But I guess it’s a cool WebAssembly experiment nonetheless.

divyenduz 6y ago
Oh absolutely, just an experiment, I am really curious about doing things like video editing etc on the client side. I did use this to delete a lot of old tweets though.
- banana_giraffe 6y ago
  SELECT substr(date,1,7) as d, count(*), min(likes+retweets) FROM tweets GROUP BY d ORDER BY d DESC; Yep, looks like you mostly tossed tweets over a year old that didn't meet some threshold. Very cool to play with in the browser.
  - divyenduz 6y ago
    Yeah, I am slowly removing myself from the internet, I don’t think that I follow anyone on any social network where ever I exist. This is also a great way to backup tweets etc. Of course I have multiple SQLite files with all the data, whenever I want to delete “more”, I just take a new Twitter dump.
Tade0 6y ago
WebSQL never reached proper standardization because there was a requirement of at least two independent implementations for that and all the available ones were based on... SQLite.
- detaro 6y ago
  All being based on SQLite wouldn't have been the problem. But it specified a database "accepting the same SQL dialect as SQLite version XYZ", and that's a fairly obvious no-go (and nobody involved thought it was worth the effort to do a better specification).
reader_mode 6y ago
WebSQL died and shipping a locked database version compiled with features you want is usually better than relying on every browser DB implementation and version supporting the stuff you want to use. The apps that need SQL aren't too sensitive to initial load/download time increase by adding a MB of WASM which can later be handled by caching.
kevingadd 6y ago
IMO, anyone given the choice between IndexedDB and "compile SQLite to webassembly and use that" would pick SQLite in a heartbeat. IndexedDB is awful in almost every possible way. It's slow, the API sucks, it's limited, etc
- divyenduz 6y ago
  Ha, would be nice-ish if browser have this pre-available, TBH most loading time is loading SQLite async, then it is instantaneous
  - divyenduz 6y ago
    But that’s a bad idea, once browser version will be locked to a database version, security updates etc would be tied and a yada yada
rasz 6y ago
mozilla killed WebSql because it lacked "developer aesthetics", now we got shit indexedDb nobody uses without middleware to ease the pain. "Aesthetics and Web Developers" 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...
devwastaken 6y ago
WebSQL is deprecated IIRC - the problem with complex databasing like SQL is that users are never meant to be querying directly on it. SQLite has a number of functions that are pointers to your own functions to override/add behavior. If a user could simply query that - poof you're SOL. Which means to be safe from the host system you have to virtualize the execution somehow - WASM is exactly that. Therefore if you wanted sqlite in a browser, you can simply compile it to wasm.

divyenduz 6y ago

Oh absolutely, just an experiment, I am really curious about doing things like video editing etc on the client side. I did use this to delete a lot of old tweets though.

banana_giraffe 6y ago
SELECT substr(date,1,7) as d, count(*), min(likes+retweets) FROM tweets GROUP BY d ORDER BY d DESC; Yep, looks like you mostly tossed tweets over a year old that didn't meet some threshold. Very cool to play with in the browser.
- divyenduz 6y ago
  Yeah, I am slowly removing myself from the internet, I don’t think that I follow anyone on any social network where ever I exist. This is also a great way to backup tweets etc. Of course I have multiple SQLite files with all the data, whenever I want to delete “more”, I just take a new Twitter dump.

Tade0 6y ago

WebSQL never reached proper standardization because there was a requirement of at least two independent implementations for that and all the available ones were based on... SQLite.

detaro 6y ago
All being based on SQLite wouldn't have been the problem. But it specified a database "accepting the same SQL dialect as SQLite version XYZ", and that's a fairly obvious no-go (and nobody involved thought it was worth the effort to do a better specification).

reader_mode 6y ago

WebSQL died and shipping a locked database version compiled with features you want is usually better than relying on every browser DB implementation and version supporting the stuff you want to use. The apps that need SQL aren't too sensitive to initial load/download time increase by adding a MB of WASM which can later be handled by caching.

kevingadd 6y ago

IMO, anyone given the choice between IndexedDB and "compile SQLite to webassembly and use that" would pick SQLite in a heartbeat. IndexedDB is awful in almost every possible way. It's slow, the API sucks, it's limited, etc

divyenduz 6y ago
Ha, would be nice-ish if browser have this pre-available, TBH most loading time is loading SQLite async, then it is instantaneous
- divyenduz 6y ago
  But that’s a bad idea, once browser version will be locked to a database version, security updates etc would be tied and a yada yada

rasz 6y ago

mozilla killed WebSql because it lacked "developer aesthetics", now we got shit indexedDb nobody uses without middleware to ease the pain. "Aesthetics and Web Developers" 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...

devwastaken 6y ago

WebSQL is deprecated IIRC - the problem with complex databasing like SQL is that users are never meant to be querying directly on it. SQLite has a number of functions that are pointers to your own functions to override/add behavior. If a user could simply query that - poof you're SOL. Which means to be safe from the host system you have to virtualize the execution somehow - WASM is exactly that. Therefore if you wanted sqlite in a browser, you can simply compile it to wasm.