3 ms·
I don't really know about the job market, but Erlang/OTP has been a very fine piece of technology for the past 30 to 40 years. Elixir is quite new (2015) and w
by linkdd 5y ago
I don't really know about the job market, but Erlang/OTP has been a very fine piece of technology for the past 30 to 40 years.
Elixir is quite new (2015) and with every release it gains in maturity, and the ecosystem is growing. IMHO, Mix was a game changer in terms of tooling.
Also, with tools like Horde[0] and libcluster[1], it became very easy to setup an Erlang/Elixir cluster on Kubernetes.
When you work with distributed systems, the OTP framework is a godsend, it's no surprise to me that it's finally getting traction.
Also, I like to use Rambo[2] to call small go/rust binaries that I ship with my Docker images, useful for features where performance is important.
[0] - https://hexdocs.pm/horde/readme.html
[1] - https://hexdocs.pm/libcluster/readme.html
[2] - https://hexdocs.pm/rambo/Rambo.html
- derefr 5y ago> Elixir is quite new (2015) I suppose you can say that; that’s when it 1.0ed. But Elixir was surprisingly stable pre-1.0; I was writing production Elixir 0.6 code at Spawngrid in 2012! Really, the 1.0 announcement felt more like a formality than anything; there was no discontinuous switch from “throwing features at the wall” to “considered engineering.” Changes to Elixir have always been considered — and props to Jose Valim for that! :)
- Zababa 5y ago> Elixir is quite new (2015) and with every release it gains in maturity, and the ecosystem is growing. One thing I really like is that it's considered mostly done. The community has the wisdom of not always trying to add new features and deprecating old ones. There's no 2.0 planned but that doesn't stop people from doing impressive work like Nx. I don't know about the ecosystem, but the language itself seem like a stable investment.