3 ms·
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.
by CHsurfer 10y ago
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.
- coldtea 10y agoThat wouldn't do much for the use cases they want to use it (multimedia, games, number-crunching etc as in the example in TFA)
- lennelpennel 10y agoIn some ways web workers feel a bit like actors. granted a poor man's actor.
- cpeterso 10y agoI'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.
- jchrisa 10y agoPlease implement!