3 ms·
Is anyone really dealing with this much data in-memory in JS? I'm just curious, as I've been at this for about 30 years now, and the only times I've dealt with
by tracker1 10mo ago
Is anyone really dealing with this much data in-memory in JS? I'm just curious, as I've been at this for about 30 years now, and the only times I've dealt with this much data, it's mostly been in streaming/etl type work, where you aren't using it all in-memory at once.
Personally, I like the for-of syntax as well as for-await-of... I kind of wish there was a promise-based version of forEach, as sometimes this syntax sits better, though I'm more inclined to use map, find, etc. over forEach. If I'm not using the indexer value, then there's not much point in using arr[i] over the for-of.
Also, in practice, I've RARELY found the need to optimize how JS is used outside refactoring a recursive algorithm when there's risk of a stack overflow.
- simonw 10mo agoIncreasingly yes. A modern browser on a good laptop can crunch on GBs of data in a browser tab at once. This makes all sorts of data analysis and visualization tasks feasible in a client-side web app where previously you would have needed a detected database server somewhere. Take a look at the https://kepler.gl/ https://kepler.gl/ demos to see quite how sophisticated this stuff can get now - millions of geospatial data points rendered entirely clientside via WebGL.
- tracker1 10mo agoThanks... the vast majority of my own experience has been a combination of line of business, banking, security and govt applications outside of scientific heavy circles, so was a genuine question, despite the downvotes.