News for hackers. Stuff that matters.
Re:Elixir vs. Erlang: a question of momentum by jacquesm on Thursday April 23, 2015 @12:53PM (#9428062)
I think in part this is because there are a few very vocal elixer proponents here on HN and this being the site where those people with scaling issues and 'erlang' style problems (which most web stuff actually is!) converge the uptake could be substantial. Erlang doesn't nearly have the 'hey look at me, I wrote a language' component but it just quietly excels at what it does (reliable, scalable). Elixer being targeted at the VM it is very well possible to have the best of both worlds.

I'm curious what will happen in the longer term, if at some point the 'upstream' providers of the erlang ecosystem will take notice of elixer and will start to cater to it and then maybe actually adopt it. Until then I'm on the fence, elixer could be great but it also could end up being abandoned as more and more warts in erlang are taken care of.

And most of those warts are cosmetic rather than real problems, the lack of libraries will hurt both languages just about the same and it would be much nicer if new libraries were written with interop in mind.

That way they will have staying power regardless of which language will eventually become dominant/stay dominant.

The erlang vm and ecosystem are very well thought out, battle hardened and solid beyond what most programmers that came into the profession past say 1998 or so are familiar with but it is clearly showing its age and elixer solves some of those problems. A more open process around erlang itself could easily take the wind out of elixer's sails.

Time will tell, it sure is interesting.

And thanks David, excellent post.

edit: it could actually be that elixer will drive developers to erlang in the longer run, the syntax is a minor nuisance easily understood after a little bit of work and the 'strings' issue is mostly a different take on an old problem that you can either work around or simply accept as part of the deal. It can throw you for a loop but not worse than the things other languages will force on you and if you think about it is actually an elegant solution, re-use the same data structure to make life easier.

If under the hood those lists would be replaced with something like the clojure ones you might be able to get rid of the performance issues entirely without affecting the code already in production (unless it was C code operating directly on internal structures of erlang).

Re:Elixir vs. Erlang: a question of momentum by phamilton on Thursday April 23, 2015 @08:28PM (#9430784)
They've gone as far as making 1 in 8 tracks at Erlang Factory about Elixir. They had José give a keynote last year and participate on a panel this year. Robert Virding (one of the creators of Erlang) is fairly active in monitoring (and participating) in the elixir mailing lists. Granted, there's always a small tone of "get off my lawn", but that's just entertaining :-).

I've mentioned this before but I'll daybit again. Protocols and Macros are the game changer. The Enumerable protocol absolutely changes the way you write code and solve problems. Doing the same thing in Erlang is just not the same.