They say time is money, but we all know that you’re giving up more than money when you allocate your time to something. Investing your time also comes with an opportunity cost. Should you learn language A, framework B, or library C next? And what kind of return will you get on that investment? It seems the good developers have a heuristic for narrowing down where best to spend their time.
So, how do you gauge if learning the Elm language is worth your precious time? We think it's worth it if you're one of the following kinds of developers:
1. Curious about FP
First, if you're simply curious about functional programming or you’ve struggled with FP concepts in another language, then you'll find Elm relatively straight-forward to learn.
For me, Elm has been the easiest way into functional programming because it combines all things FP with (and this is the most important part) the ability to create something, for example a reactive web page. Elm goes beyond the theoretical. Its syntax is clean and readable, and you can build practical stuff with it quickly.
2. Front-end Programmers
3. Language Nuts...