I feel like this article lacks a lot of details that would make his point. I've spent the past few weeks learning F#, and I see nothing in this article that makes it clear why Elixir is more "empathetic" than F#.
As part of my "job", I end-up playing, using and reading a lot about functional programming languages and I like F# a lot. It feels like the team behind F# put a lot of effort in transmitting the concepts in an accessible and clear way (F# Workflow in my opinion are one of such examples). It is not surprise given Microsoft has been introducing functional concepts into languages like C# and VB for a long while.
For Elixir, I have put extra attention into how you to get started with the language because it is not only about learning a functional language (and thinking in terms of recursion, immutability, etc) but also about concurrency and building fault tolerant applications. So help and guidance on every step really matters.
Documentation is extremely important and must be easily accessible. The language should be easy to explore, in your editor or terminal. Error messages should be clear: if you read an error and you don't know what to do next, it is a compiler bug.
I hope I have answered your question. I also would like to say it is not about finding the most empathetic language. They will all have pros and cons, many times even depending on the developer previous experience.
Thanks for a thoughtful answer. I'm with F# regardless of its particular merits (I'm lucky enough to have the privilege to write F# when the other coders here work in C# as it is), but I wish you the best of luck with your project.
As part of my "job", I end-up playing, using and reading a lot about functional programming languages and I like F# a lot. It feels like the team behind F# put a lot of effort in transmitting the concepts in an accessible and clear way (F# Workflow in my opinion are one of such examples). It is not surprise given Microsoft has been introducing functional concepts into languages like C# and VB for a long while.
For Elixir, I have put extra attention into how you to get started with the language because it is not only about learning a functional language (and thinking in terms of recursion, immutability, etc) but also about concurrency and building fault tolerant applications. So help and guidance on every step really matters.
Documentation is extremely important and must be easily accessible. The language should be easy to explore, in your editor or terminal. Error messages should be clear: if you read an error and you don't know what to do next, it is a compiler bug.
I hope I have answered your question. I also would like to say it is not about finding the most empathetic language. They will all have pros and cons, many times even depending on the developer previous experience.