3 ms·
> with non-blocking I/O, you don't need hundreds of threads That stands true. No need to use Workers for IO. We won't suddenly have to use it, because it does
by the_gipsy 10y ago
> with non-blocking I/O, you don't need hundreds of threads
That stands true. No need to use Workers for IO. We won't suddenly have to use it, because it does not solve a problem for most of us (like promises did, for example).
> start driving complex UI in multiple web workers
I would guess that for 99% of UIs, it would be total overkill to use Workers (you could still offload e.g. AI, in a game).
In general, the push comes from WebGL and similar heavy stuff.
> something like react-parallel
I definitely can see it, especially with redux. Just for the sake of it, someone somewhere will try it.