As a disclaimer: I didnt delve deeply into ReasonReact nor Reason since i’m still looking for a reason (pun intended) to switch from learning elm to learning reason, what intrigues me is the approach that ReasonReact is using when assimilating React into reason:
It is my impression that ReasonReact is trying way too hard to make creating ReasonReact components look like class components using a notation similar to objects or classes by creating a record/object using one of ReasonReact component functions and then spreading them into records/objects that we create.
Why this approach? React is, afaik, pushing to making functional components since they have more room for low level improvements than using class based components. Why cant ReactReason components be simple functions? I can make perfectly working solutions using only functional components in react and only using hooks and class components when trying to improve performance by manipulating the life cycle events.
My impression is that ReasonReact is only mapping functionality over to reason and not using reason (or any other ml lang) strengths.