News for hackers. Stuff that matters.

A comment on Concurrent JavaScript: It can work. Parent comment

Re:Concurrent JavaScript: It can work by rmrfrmrf on Wednesday August 30, 2017 @03:55PM (#15135413)
For that matter, anyone who'd like to have "fun" with concurrency and lock management in browser-side JS is free to play around with recurring asynchronous data fetching cached in localStorage when multiple browser tabs are open.

Spoiler: locks are the wrong approach and you should be relying on events/callbacks instead. Oddly enough, that's similar to my gut feeling about Threads in JS.

[ Parent | on HN ]
Re:Concurrent JavaScript: It can work by einrealist on Wednesday August 30, 2017 @04:31PM (#15135748)
A browser can easily optimise HTTP or localStorage calls internally, without introducing Threads to the "userland" code.
[ Parent | on HN ]
Re:Concurrent JavaScript: It can work by rmrfrmrf on Wednesday August 30, 2017 @07:13PM (#15136907)
I'm talking about a userland implementation.
[ Parent | on HN ]