4 ms·
It's a shame that the elegance of Erlang has been distorted with Elixir.
by fortran77 7y ago
It's a shame that the elegance of Erlang has been distorted with Elixir.
- brightball 7y agoWhat’s been distorted?
- rlander 7y ago"The language should be simple – Simple in the sense that there should be a small number of basic principles, if these are right then the language will be powerful but easy to comprehend and use. Small is good."
- jeremyjh 7y agoElixir has Erlang semantics + hygienic macros and a few other niceties. Judicious use of macros in libraries can actually make the experience simpler for the developers.
- rlander 7y agoIf both languages have the same semantics, why choose the one with more complex syntax?
- keymone 7y agoSyntax complexity is highly debatable topic. It involves complexity of parsing (by machine), reading and scanning(by human), conciseness, coherence of syntactic constructs and more things I don’t know. I wouldn’t say prolog based syntax is necessarily simpler than ruby(?) based one in all those categories. Of course only LISPs have achieved syntax perfection, all hail LFE and other lispy fronts to erlang!
- toast0 7y agoI don't particularly care for Elixir, but it's kind of nice having more people on the BEAM.
- BoorishBears 7y agoI don't think the above comment is put in the best way... But I do have a certain duality about my feelings on Elixir On one hand, yes, it is cool to see more adoption of BEAM, I do wish Erlang could have done that by itself. I vastly prefer Erlang to Elixir and find it does slightly... taint the simplicity and cleanliness of the syntax Erlang made made me fall in love with, just to be Ruby-like. I don't feel it actually benefits the language at all past the meta reason of attracting Ruby-ists (which again, isn't necessarily a bad thing by itself)
- jeremyjh 7y agoThe advantage isn’t Ruby syntax - it’s the macro system.
- BoorishBears 7y agoMacros are the perfect example of things that go against the core of why I love Erlang. Erlang actively makes it hard to write hard to maintain systems because it's syntax is so lean, there's no way to make your FactoryFactoryBeanFactory Macros can easily be abused, and to me the biggest gain I've seen is removing OTP boilerplate, which is not that much compared to what you get out of it I will say I haven't used Elixir in anger so I don't know if people are doing more with it now, but I'd just rather not have it.
- rlander 7y agoI feel the same way. Elixir users keep banging on the macro drum but most Erlangers don't want them. I can read any Erlang program I wrote 10 years ago with ease. I have difficulty understanding a small Elixir project I wrote just a few months ago.
- jeremyjh 7y agoIt’s a shame this thread has to be spoiled by off-topic criticism of another language. Why even bring it up? You can promote Erlang without tearing down Elixir.
- faitswulff 7y agoNotably not the impression Joe Armstrong, creator of Erlang, had when he tried Elixir out for a week: > This is good shit. The funny thing is that Erlang and Elixir are the same thing under the surface. They “feel” the same to me. https://joearms.github.io/published/2013-05-31-a-week-with-elixir.html https://joearms.github.io/published/2013-05-31-a-week-with-e...