September 10th, 2019
This means it has one call stack and one memory heap.
There has been an interesting point/counter-point combo recently along these lines.
You should always use Web Workers.
There are lots to consider, of course, but I like how he compares this to how other languages call the main thread the “UI thread.” If what you are doing is UI-related, do it on the main thread; if it’s not, do it off the main thread. An example? State management.
David Gilbertson must have read that and wrote:
I saw an article recently making the case that updating a Redux store was a good candidate for Web Workers because it’s not UI work (and non-UI work doesn’t belong on the main thread). Chucking the data processing over to a worker thread sounds sensible, but the idea struck me as a little, umm, academic.
(Looking at that 100ms thing, it’s worth noting that a major point Das Surma is making is that the world is full of low-end phones — and who knows what 100ms on a high-end phone is when translated to on a low-end phone.)