I’m diving head-on into the Reason ecosystem, and really enjoying it so far. To start, I’m building a small full-stack web application that I’ve wanted to build for some time so that I can learn via a practical application. I want to use Reason for the frontend and backend. My question / topic is this:
There seems to be a pretty big disconnect between Reason on the JS platform via BuckleScript and Reason Native. For example, incompatible build systems (bsb vs. esy) and test runners (a JS test runner, i.e. Jest vs. Rely). I understand it’s early days for Reason Native, and Reason as a whole really. But for my application where I’m trying to have isomorphic Reason code, Reason Native seems like the wrong choice for the backend. I’m simply using Express via bs-express on the backend, and I’m able to share code freely between the front and backends. This is important to me architecturally, as I’m experimenting with architectures that exploit this ability to share code.
I wanted to look into Reason Native for the server, but it seems much easier to just double-down on JS as the platform for hosing Reason. So how much is the community focusing on Native, and what’s the main use case for Native? Should we be making the JS Reason ecosystem more mature before focusing on Native? How do we feel about Reason-on-JS being the main platform for now?