You're right in that ReasonML syntax is a bit of a moving target, but I think it's part of the initial pains of their effort to provide an approachable port int

You're right in that ReasonML syntax is a bit of a moving target, but I think it's part of the initial pains of their effort to provide an approachable port into the ML world. The syntax should stabilize eventually. The maintainers are aware of the churn they are creating, and have deemed it worth it. That being said, I have a bunch of old projects written in Reason 2 (which still work; the tooling has preserved perfect backwards compatibility[0]), and recently started a new project using the new Reason 3 syntax. It was easy enough to pick up the new syntax in about a day. I haven't done it yet, but my understanding is that it's completely automated[1]. [0]: https://reasonml.github.io/community/blog/#reason-3 https://reasonml.github.io/community/blog/#reason-3 [1]: https://github.com/reasonml/upgradeSyntaxFrom2To3 https://github.com/reasonml/upgradeSyntaxFrom2To3