Re:A Taste of JavaScript's New Parallel Primitives
by CHsurfer on Thursday May 05, 2016 @02:21PM
(#11638544)
I keep hoping that JS would evolve to support the actor model, a la Erlang/Elixir, with their process based persistence, concurrency via message passing, etc. It just seems so much simpler and tractable than this proposal.
[ Parent
| on HN ]
Re:A Taste of JavaScript's New Parallel Primitives
by cpeterso on Thursday May 05, 2016 @04:08PM
(#11639296)
I've seen projects to compile Erlang to JS, but has anyone experimented with a JS compiler that targets Erlang's BEAM VM like Elixir?
JS is an approachable language but Node has problems with scaling and error handling of non-blocking IO. Erlang solves those problems but the language is not approachable and has a smaller ecosystem than JS. I'm imagining something like Node with "micro-workers" so developers could reuse their existing JS code, but not have to worry about scaling or non-blocking APIs.
Re:A Taste of JavaScript's New Parallel Primitives
by jchrisa on Thursday May 05, 2016 @10:32PM
(#11641294)
Please implement!
Re:A Taste of JavaScript's New Parallel Primitives
by coldtea on Thursday May 05, 2016 @03:04PM
(#11638865)
That wouldn't do much for the use cases they want to use it (multimedia, games, number-crunching etc as in the example in TFA)
Re:A Taste of JavaScript's New Parallel Primitives
by lennelpennel on Thursday May 05, 2016 @03:28PM
(#11639025)
In some ways web workers feel a bit like actors. granted a poor man's actor.