> So in reality, it's a little bit crazy to expect the Reason users to be the ones rapidly changing the toolchain. That's too bad, because all of the marketing

> So in reality, it's a little bit crazy to expect the Reason users to be the ones rapidly changing the toolchain. That's too bad, because all of the marketing (at least around the time I initially looked into it) was something like "OCaml for humans". The JS bit was mentioned as a footnote, but then when I looked at it, JS was the primary target. I was half hoping that Reason would fix some problems that keep me (and probably many others from OCaml): * Fragmented build tooling ecosystem with no outstanding options (ideally the Reason community would build a standard tool that improves on other options) * Fragmented standard library ecosystem with no outstanding options (ideally the Reason community would standardize on a std lib, but this might be overly optimistic) * Syntax (obviously this is Reason's target problem, but not the most important issue) * Parallelism (well, Reason probably would never address this one)