> Compare that to SQLite's 1.2mb of wasm and glue code
replyThe current trunk is actually 1.7mb in its canonical unminified form (which includes very nearly as much docs as JS code), split almost evenly between the WASM and JS pieces :/. Edit: it is 1.2mb in minified form, though.
Disclosure: i'm its maintainer.
Edit: current trunk, for the sake of trivia:
sqlite3.wasm 896745
sqlite3.mjs 816270 # unminified w/ docs
sqlite3.mjs 431388 # unminified w/o docs
sqlite3.mjs 310975 # minifiedI think actually this competes with the old BerkeleyDB: https://en.wikipedia.org/wiki/Berkeley_DB - which I now see is no longer BSD-licensed, and in any case has been rendered almost extinct by SQLite. It was used for basic on-disk key-value store work.
replyEven BerkeleyDB tries to be mutable. What I'm doing doesn't need the mutability so it's much more similar to dictionary formats (though probably simpler) than it is to a database. Though a lot of people do use full databases for immutable dictionary key-value stuff. I just couldn't get any database to work well enough for a pwa dictionary.
replyMany comments here to your creation, PeakSlab, but not yet a dedicated praise. I didn't know it but I have to say it is really cool and innovative! The performance of the dictionary is indeed superb and I will definitely bookmark this for future reuse. So, in a nutshell: thanks for sharing!
replyA more standard solution would be cdb.[0] Although that doesn't support compressed data.
reply[0] https://cdb.cr.yp.to/ , https://en.wikipedia.org/wiki/Cdb_(software)
It is crashing Safari.
replyPerhaps a dumb question, but how do you get data into it if you’re not doing writes
replyI think it's just immutable once you've generated it. No need to update indexes or check consistency on writes, no need for transactions, etc.
replyGenerate it one time from a source tsv file or folder of media.
replyThink historical records of, say, share values for past years. You might have a single db for 1900-2000, for instance. Things like that.
replyNot everything needs to be real-time updated.
something something XKCD competing standards something something
replyCreating something new for a different use case isn't pointless. It's like comparing inline skates to ice skates.
replyBelieve me, I tried sticking to SQLite or aard2 or stardict, they just were fundamentally inadequate with no good pwa cross platform tooling.
replyDoes this remain true now that SQLite has a WASM build?
replyYes, because originally when I started PeakSlab it used the SQLite wasm build.
replyDoesn’t even apply unless someone says that (1) there are too many “standards”, and (2) so we are making this standard (neither apply here). Someone made something.
replyWe should really consider eventually retiring memes because they just end up as thought-terminating cliches.
This is of course referring to xkcd #927. How do I know that?