News for hackers. Stuff that matters.

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

Re:Concurrent JavaScript: It can work by spankalee on Wednesday August 30, 2017 @01:59PM (#15134413)
Then add immutable objects to JS, which enable a host of other optimizations and are useful in single-threaded contexts too.

Shared-memory multithreading is just very difficult to use correctly. Actor-style concurrency hasn't really caught on (possibly because of the poor performance of workers and postMessage), but there is probably a middle ground that's easier for developers to get right.

[ Parent | on HN ]
Re:Concurrent JavaScript: It can work by amelius on Wednesday August 30, 2017 @04:16PM (#15135602)
I don't think it is a good idea to stray away from the bare metal in this case. We're trying to bootstrap other languages on top of JS. They can introduce their own abstractions to shield off the programmer. Just my 2ct.
[ Parent | on HN ]
Re:Concurrent JavaScript: It can work by phailhaus on Wednesday August 30, 2017 @02:02PM (#15134440)
JS already supports immutable objects, by using Object.freeze().
[ Parent | on HN ]
Re:Concurrent JavaScript: It can work by bzbarsky on Wednesday August 30, 2017 @03:20PM (#15135082)
That doesn't really make things immutable. Even ignoring the deep vs shallow issue, consider what effect Object.freeze has on a JS Map (hint: none, really; you can still add/remove things).
[ Parent | on HN ]
Re:Concurrent JavaScript: It can work by phailhaus on Wednesday August 30, 2017 @03:44PM (#15135305)
Right, that's where libraries like ImmutableJS come in.
[ Parent | on HN ]
Re:Concurrent JavaScript: It can work by spankalee on Wednesday August 30, 2017 @02:04PM (#15134456)
That's not deeply immutable like you'd want for sharing objects across threads, or even for using in contexts like React and Redux.
[ Parent | on HN ]
Re:Concurrent JavaScript: It can work by phailhaus on Wednesday August 30, 2017 @02:16PM (#15134566)
Not too hard to call Object.freeze() recursively to get the deep immutability you need. And of course there's ImmutableJS for other immutable data structures.
[ Parent | on HN ]