We strongly believe that the ReScript compiler and syntax will provide the best experience to write JS and React applications. Unifiying the tools in one coherent platform and core team allows us to build features that wouldn’t be possible in the original BuckleScript + Reason setup.
This has no impact on the development of Reason. On the contrary, Reason can now focus on their goals, as much as we can focus on ours.
What Will Change with ReScript?
Technically, not much. One of our main goals is to keep backwards compatibility for existing BuckleScript codebases and will provide an automated upgrade path from
The BuckleScript compiler toolchain and its new
.ressyntax will be unified into one platform called ReScript. Upgrading from the bs-platform to the soon-to-be-published ReScript npm package will just be a matter of updating your package.json file. Syntax wise, we believe that previous Reason users will feel right at home.
ReScript will continue shipping the old Reason v3.6 syntax as well and it will be possible to mix
.resfiles in one codebase (same with libraries).
Turns out there is a Discourse forum, too:
I’m very sad about this, because it seems to be the result of in-fighting in the community. Everyone is doing their best to keep things polite, but basically it looks like BuckleScript is sick of ReasonML and wants to eject them from their community and are doing so by taking over their brand.
That’s a shame.
We experimented with ReasonML early on and determined that TypeScript was the right balance of broader understanding by external users for now.
Still interested in languages / frameworks that look like this.