5 ms·

this might be the tipping point of js fatigue for most React/JS developers. we can only hope this doesn't catch on, fingers crossed.

TheAceOfHearts 9y ago
If it's ends up being notably superior in multiple ways, and you already have a properly configured and flexible build toolchain in place (i.e. Webpack), adding support should be trivial. I haven't personally used it, but a quick search landed me on the bs-loader [0] repo, which claims to work with both OCaml and Reason files. As I understand it, and I'm not very familiarized with Reason, the team behind the project is working hard to have a good interop story. We've seen the same thing with React's versioning scheme [1]! Going forward there shouldn't be horrible breaking changes, and in the cases where stuff must be broken, they appear to commit to providing a clear migration path that can be adopted gradually. There's probably plenty of good use-cases for using something like Reason. Should it be used everywhere? No, certainly not. But having worked on a reasonably sized JavaScript web app, my experience has been that it becomes increasingly difficult to maintain as it grows. Even with something like Flow or TypeScript, you have to think very carefully any changes. Luckily, the JavaScript ecosystem has modularized everything quite heavily, so you can usually contain things that end up being "bad ideas" and gradually chip away at em. The app I worked on wasn't even that large or complicated, so I have a very hard time wrapping my head around the challenges faced by engineers working on Facebook's scale. [0] https://github.com/rrdelaney/bs-loader https://github.com/rrdelaney/bs-loader [1] https://facebook.github.io/react/blog/2016/02/19/new-versioning-scheme.html https://facebook.github.io/react/blog/2016/02/19/new-version...

5 ms·

this might be the tipping point of js fatigue for most React/JS developers. we can only hope this doesn't catch on, fingers crossed.

by jaequery 9y ago

TheAceOfHearts 9y ago
If it's ends up being notably superior in multiple ways, and you already have a properly configured and flexible build toolchain in place (i.e. Webpack), adding support should be trivial. I haven't personally used it, but a quick search landed me on the bs-loader [0] repo, which claims to work with both OCaml and Reason files. As I understand it, and I'm not very familiarized with Reason, the team behind the project is working hard to have a good interop story. We've seen the same thing with React's versioning scheme [1]! Going forward there shouldn't be horrible breaking changes, and in the cases where stuff must be broken, they appear to commit to providing a clear migration path that can be adopted gradually. There's probably plenty of good use-cases for using something like Reason. Should it be used everywhere? No, certainly not. But having worked on a reasonably sized JavaScript web app, my experience has been that it becomes increasingly difficult to maintain as it grows. Even with something like Flow or TypeScript, you have to think very carefully any changes. Luckily, the JavaScript ecosystem has modularized everything quite heavily, so you can usually contain things that end up being "bad ideas" and gradually chip away at em. The app I worked on wasn't even that large or complicated, so I have a very hard time wrapping my head around the challenges faced by engineers working on Facebook's scale. [0] https://github.com/rrdelaney/bs-loader https://github.com/rrdelaney/bs-loader [1] https://facebook.github.io/react/blog/2016/02/19/new-versioning-scheme.html https://facebook.github.io/react/blog/2016/02/19/new-version...