kai zhu

+1

kinda leaning against at moment ... - pro - do see some benefit in ergonomics - con - impacts program-correctness with subtle, order-related bugs when property-names collide - messes up...

yep, hence the empty `{}` in `Object.assign({}, ...)` to avoid mutating the first object.

here is diff-comparison of the 12 places where "deadcode" was replaced with assertion-checks in jslint to get full-code-coverage @ https://github.com/jslint-org/jslint/compare/v2020.11.6..v2021.5.30#diff-4822639e8179a5188bdfd8cfb48d9e103a7dcc1f2b1036465ab7017d4166c2a8 the purpose of this issue is to track regression/blame in...

i agree with lovasoa its probably not feasible to re-invent new mechanism to persist individual sqlite-records to indexeddb. what we really need are native file-api's like "seek" exposed in browser...

The largest sqlite db I've managed to persist in indexeddb is ~235mb. Chrome doesn't allow indexeddb objects larger than that. For applications with many persisting writes, I had to redesign...

chrome-canary recently shipped with experimental native-filesystem support for webassembly (with database use-case specifically in mind). they have a tutorial to compile wasm's with native-filesystem-support [here](https://github.com/fivedots/nativeio-porting-tutorial). note there's some conflict between...

I'm a windows user, who runs linux stuff under debian docker. don't know about wsl2, but was not impressed with wsl1 -- things would randomly crash under it. i don't...

localforage/indexeddb has a hard limitation in chrome as well of ~240mb per sql.js database. its probably enough for most, but don't expect to do gigabyte-scale, persistent data-science in browsers anytime...

i have an idea to provide a minimal-maintennance promise-based worker in ~100 lines of code in `src/api.js`. will provide a pull-request of it to see what you think. been using...