thougthfulness of facebook's reasonml and reasonreact

Facebook recently released 0.3 version of reason and reasonreact for creating UIs. Instead of using typescript, you would use reasonml. reasonml is based on OCaml which has both functional and OOP capabilities.
Why is how facebook is integrating reasonml into their ecosystem brillant?
  • facebook recognizes that the ocaml syntax is a burden to learn. reasonml is a more javascript oriented syntax of ocaml. ocaml syntax is, as many functional languages are, harder to learn than say google’s go or really it’s difficult if you are not used to functional syntax. syntax is a big burden for migration of existing devs. The great part is that they are making it easy for a certain group, such as js programmers, to migrate.
  • facebook has created reasonreact using only a subset of ocaml. No OOP components. And they reduce the surface area of the reactjs APIs to something appropriate for the functional world. The API is small and easy to learn. It does not offer everything that the reactjs API offers but by not making the reasonreact hard, they can get started easily with a subset of react capabilities.
  • You can migrate one “file” at a time to reasonml which does not require you to migrate “everything” at once. Interop is good enough to make this doable. reasonml also has the ability to output .d.ts files for those using typescript in everyday use so that your code has some typechecking.
The expectation is that you would use reasonml instead of typescript. reasonml has immutability, currying by default and other things that typescript, as a superset of javascript, does not have built in. Both have a place.
You can also get the same benefits of reasonml using scala.js which has a reasonreact like wrapper plus a few other facades to choose from.

Comments

Post a Comment

Popular posts from this blog

quick note on scala.js, react hooks, monix, auth

quick note on scala.js, react hooks, monix, auth Reactjs hooks finally came out of preview in a recent version of React. scalajs-reaction has had support for hooks since they were in preview. React hooks seem like the hot new thing but for me the question is, do hooks help improve your code by improving maintainability, time to market, TCO, etc.? Let’s take a look using authentication as an example and employ monix , a reactive observable framework that also builds on cats . We will assume we are building a SPA. Does it improve your code and make your application & development experience better? Auth Auth processing can be complex. Many react auth examples you find in blogs like to show how to use “react-routing” and “auth” as a switch that determines which routes are protected or unprotected. Protected routes show application specific data. Unprotected routes show login content . Based on storing a “User” object in the browser session/local storage, th...
Read more

zio environment and modules pattern: zio, scala.js, react, query management

zio environment and modules pattern: zio, scala.js, react, query management This blog covers a zio-based fetch design for scala.js, react web applications. It heavily uses the zio “environment” feature to help motivate a point of view on the modules pattern in effect systems. At the end, I summarize some thoughts on ergonomics and complexity. This blog assumes a basic knowledge of zio and react. scala.js is just like scala so you mostly already know scala.js. This blog is a follow-on to previous blogs: https://appddeevvmeanderings.blogspot.com/2019/10/scalajs-react-fetcher-hook_48.html and https://appddeevvmeanderings.blogspot.com/2019/11/scalajs-and-react-suspense.html . I have been keeping an eye on and culling ideas from typscript/javascript fetching libraries that address query management concerns. The formulation below incorporates some of those concerns but does not try to comprehensively duplicate well established javascript libraries. I only care about ...
Read more

attributes with react and typescript.md

If you use typescript with react you may wonder what the right signature is for your “properties” interface. Obviously, your component will have few to many specific properties that reflect your domain. However, you may wish to also provide for the ability to add other attributes, such as those valid for a div property. In other words, you want to extend your props interface with that of the properties from a div element. How do you do that? There are really two issues: How do you extend your props interfaces How do you filter the props once you receive them to just those that apply. Extend Your Prop Interface or Use Sum Types It’s not uncommon to see interface Props { className ? : string yourProp ? : number } with the idea of using it in class MyComponent extends React.Component<Props, any> somewhere. If your component will have an outer div, you may also pass in a react element so that its configurable. But let’s say your outer element is a div and you wan...
Read more