Concurrent JavaScript: It can work

Re:Concurrent JavaScript: It can work by stupidcar on Wednesday August 30, 2017 @02:53PM (#15134864)

Of course not, and hopefully it will come to V8, but its mere existence does not preclude enhancing JavaScript, any more than the existence of PInvoke or JNI precludes enhancing .NET and Java.

When people say "JS shouldn't support feature X", when feature X is supported in every other serious language, I can't help but guess that their real problem is with JS itself, and they just don't think people should be using it at all. Fine, if that's their opinion, but they should come right out and say it.

[ Parent | on HN ]

Re:Concurrent JavaScript: It can work by chrisco255 on Wednesday August 30, 2017 @04:14PM (#15135592)

Well for me it adds complexity to JS. One nice thing about JS is that it is single threaded and you don't have to deal with locks or inconsistencies there. An entire class of problems goes away, and since JS event loop is reasonably fast as it is, it's pretty nice not having to worry about concurrency.

[ Parent | on HN ]

Re:Concurrent JavaScript: It can work by threatofrain on Wednesday August 30, 2017 @09:23PM (#15137446)

I would think that it's owing to the frequently single-threaded context of JS that concurrency becomes even more vital for maintaining the liveliness of your app. I also think that identifying aspects of concurrency often means free parallelism speedups, and the user doesn't even have to be aware -- no extra mental price.

[ Parent | on HN ]

Re:Concurrent JavaScript: It can work by pizlonator on Wednesday August 30, 2017 @02:58PM (#15134921)

So true!

Lots of people actually like using JS. I think it makes sense to understand what features can be added to this language.

[ Parent | on HN ]