4 ms·
It would be nice if you elaborated on what those problems are and how elixir solves them better than existing alternatives. All I ever see is people exclaiming
by preommr 7y ago
It would be nice if you elaborated on what those problems are and how elixir solves them better than existing alternatives.
All I ever see is people exclaiming how awesome it is and then the responses turn out to be underwhelming for various reasons. Like hot reloading isn't that special or unique anymore.
- gregors 7y agoI feel like this talk does a great job of answering that question - The Soul of Erlang and Elixir by Saša Jurić (https://www.youtube.com/watch?v=JvBT4XBdoUE https://www.youtube.com/watch?v=JvBT4XBdoUE)
- preommr 7y agolol, there's the hot reloading. But that's an interesting talk. I didn't have time to go through the whole thing but the core of it seems to be the pros of erlang like BEAM's high concurrency advantages and uniformity of tools running on top of otp. It's an interesting argument.
- brightball 7y agoI need to write about it more. The most in depth piece I've written was this one: https://blog.codeship.com/comparing-elixir-go/ https://blog.codeship.com/comparing-elixir-go/ Hot reloading is very unique though (but not necessary for most use cases). There's no other stack outside of the BEAM that has an equivalent. A lot of what is offered by the BEAM isn't even possible in other stacks because it requires a collective of language decisions working together.