3 ms·
Considering the production system that the Erlang VM has been deployed to(and the length of time it's existed and thrived) it's hard to make an argument to re-i
by vvanders 10y ago
Considering the production system that the Erlang VM has been deployed to(and the length of time it's existed and thrived) it's hard to make an argument to re-invent it in another language.
If that's what your domain space needs, use the BEAM and find a way to talk to it for the parts that you can't move to Erlang.
- dgfgfdagasdfgfa 10y agoIt's not hard to justify; that's laughable. It's simple redundancy!
- techdragon 10y agoSometimes the concurrency benefits just don't add up when compared to other business/project concerns. I say this as an big fan of Erlang, truth is, sometimes you just have to accept that your job is to write a python/Django backend without a line of JavaScript in order to serve as a line of business app, and if the load gets bigger, you just throw another server at it. That said, erlang is great, elixir is awesome, and both are 100% worth every developers time to learn.
- dgfgfdagasdfgfa 10y agoI'm not sure where concurrency plays into this at all.