3 ms·
I think my question is why do this if JavaScript is a single threaded language anyway? If you’ve got concurrent processes running in JavaScript, they’re not act
by gnarlouse 3y ago
I think my question is why do this if JavaScript is a single threaded language anyway? If you’ve got concurrent processes running in JavaScript, they’re not actually “concurrent”, right? If you’re stuck using JS aren’t you fundamentally better off separating them into two distinct process packages, and having them communicate via some IPC system?
Furthermore; why not just *avoid doing concurrency intensive work in JS* in the first place? Isn’t that why people learned Go?
Seems like a solution looking for a problem kind of, but that’s my low effort critique so maybe I should stuff it.
- joeycumines 3y agoI'm working on improving documentation and examples, still a WIP, but you may find this interesting: https://news.ycombinator.com/item?id=38183241 https://news.ycombinator.com/item?id=38183241
- gnarlouse 3y agoI mean isn't this what we have RxJS for?