A Front-End Developer with a passion for learning how people work, the efficacy of good design, and a growing interest in the complexities of functional programming.
I don't think it would be more or less fair. The point was to show the similarities and how they are not much different, in order to get more people interested in it. If I compared Elm to Reason then not many people would relate to it.
Absolutely. Both are statically typed languages which compile down to JS (strictly speaking, not ReasonML, but Bucklescript) with a sound type system (other than typescript).
But imho Reason is easier to learn for JS developers, especially React developers, because of syntax similarities. Also, interop (which you probably will need in a bigger project) is better in Reason.
Elm is a cleaner approach though, and is very fitting for smaller, self-contained projects.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Would it be more fair to compare Elm to ReasonML?
I don't think it would be more or less fair. The point was to show the similarities and how they are not much different, in order to get more people interested in it. If I compared Elm to Reason then not many people would relate to it.
Good idea !!
Absolutely. Both are statically typed languages which compile down to JS (strictly speaking, not ReasonML, but Bucklescript) with a sound type system (other than typescript).
But imho Reason is easier to learn for JS developers, especially React developers, because of syntax similarities. Also, interop (which you probably will need in a bigger project) is better in Reason.
Elm is a cleaner approach though, and is very fitting for smaller, self-contained projects.