News for hackers. Stuff that matters.
Re:Concurrent JavaScript: It can work by spankalee on Wednesday August 30, 2017 @02:03PM (#15134449)
Yes. Presumably transferrable objects would have to be created on a shared heap. Non-transferrables would live on thread-local heaps.
Re:Concurrent JavaScript: It can work by pizlonator on Wednesday August 30, 2017 @02:45PM (#15134796)
I find that thinking about multiple heaps is harder than thinking about threads. (Ever programmed with scoped memory? It's a nightmare.)

I find that thinking about transferrables is harder than thinking about threads. It's gross that an object suddenly loses all of its state just to give that object to another thread. Then, other parts of your code that still want access to that data have to do things that are definitely more gross than acquiring a lock.

Re:Concurrent JavaScript: It can work by amelius on Wednesday August 30, 2017 @04:23PM (#15135668)
You don't need locks to access immutable objects (except perhaps for garbage collection).

But I agree that transferring control is a bad idea.