| Agreed that the concurrency gap has narrowed in certain cases or either people don’t care, but I have always seen concurrency/distribution as “enablers”. You can have the best concurrency story in the world, but if you don’t have good tooling or you don’t focus on the DX, then people will just leave (or perhaps not even start). Concurrency/distribution is what allows Phoenix to be a real-time, productive, and scalable web framework on its own. Nerves rely on fault tolerance to bring sanity to embedded systems. And so on. In turn those are led by teams who saw the language features and noticed they addressed many issues they were struggling with in other platforms. But at the end of the day, for languages like Elixir, the frameworks and tools are much better equipped to attract developers than “raw” language features. PS: disagree on the Erlang VM bit. JIT, dirty NIFs, and maps immediately come to the top of my head as big and important changes in the last 10 years. There have been many usability focused changes in the last 2 years too, in error messages, the shell (upcoming), etc. |