681 karma · joined September 26, 2013
It is essentially a big pile of macros, so sometimes number of keywords that you have to keep in your head is staggering. Also, Elixir is a pretty big language - I knew Erlang before diving into it - so the barrier and number of concepts that you have to get familiar with is huge. Don't get me wrong - all these concepts/design patterns are necessary (I am thinking about BEAM and OTP here). Erlang (and therefore Elixir) is complete as development environment, that's where the amount of knowledge is coming from.
Cool intro to erlang/BEAM: http://www.slideshare.net/BrianTroutwine1/erlang-lfe-elixir-...
No one sane will run docker on prod anyway.
> Scala is the programming language I use for tasks like writing web servers or IRC clients.
Product always goes first.
You can run multiple apps on the same VM and they will run concurrently and communicate with each other using protocols that are core of the language.
I agree, erlang seems weird at first, simply because there is not anything like it. It also solved todays problems with software a decade ago.
Capitalism! :)
Also as many people here pointed out, RMQ is a single point of failure which might be acceptable for some cases. To me, the problem is that by design this architecture has a bottleneck which is really hard to get rid off.
Also, yes, I think concurrency model in node.js is the worst possible one.
* swift2 (iOS)
* elixir, phoenix framework, ecto (not that new to me, but I've never shipped anything to prod with it)
* elm - javascript replacement
Everything that is completely different from your current "stack" will give a new perspective... JS dev? Try elm, look a pure functional languages.
I meant to troll, sorry.
1. Language forces you to model-view-controller style
2. Language makes the model immutable
3. Language forces you to use correct types which saves a lot of trouble.
On the other hand, I a new to frontend - so I might be wrong.
https://www.youtube.com/watch?v=csyL9EC0S0c&feature=youtu.be...