4 ms·
Thank you for the useful clarification. From what you write, it sounds like in production that, if one is attracted by the BEAM, there is less risk in choosing
by delhanty 9y ago
Thank you for the useful clarification.
From what you write, it sounds like in production that, if one is attracted by the BEAM, there is less risk in choosing Erlang than Elixir.
One thing that concerns me for production use is the combination of the Erlang license and the possibility of Ericsson "doing a Sun" by selling the technology to Oracle, which might lead to an Android like situation.
- im_down_w_otp 9y agoWell... Elixir has a thriving community around it right now. Erlang has a lot of really mature libraries and frameworks. It's trivial to include Erlang in an Elixir project, it's slightly less simple to go the other way, but it's still doable. In either case I don't think you have much in the way of risk regarding Ericsson pulling a Sun. When I say Ericsson is "disinterested" I just mean they're not inclined to promote or progress the language with the kind of pace and/or hype required to keep a thriving and active Silicon Valley shaped community going. It's a tool that works well at exactly what it was designed for. There's no driving force trying to move it further to take over the general purpose programming world like Java had or Go has. Anyway, we're epically off topic :-) I think my email is in my HN profile, so happy to take this offline.
- delhanty 9y agoTrue - we are way off topic! Sorry and thank you again - was very interested in your experience.