reason-react

https://github.com/reasonml/reason-react/issues/199#issuecom... It's one of the big reasons our company isn't even considering ReactReason at present. Lack of support for version 16 APIs is killer when you already have stuff depending on them.

I’m curious what the shape of your redux state tree and component tree looked like. It sounds like you had a collection of n components, each with its own autocomplete component. Was there not an obvious parallel in the redux state tree for each of these n components? Also, as a side note, you may want to check out recompose’s withReducer HOC, which is effectively a way to use the Redux action+reducer flow to manage the state of a single component (without the separate store, the context stuff, etc. that Redux provides): https://github.com/acdlite/recompose/blob/master/docs/API.md... In case you’re interested, ReasonReact also provides a reducer component as the only way to have a stateful component. The pain of “boilerplate” basically goes away in a typed language: https://github.com/reasonml/reason-react/blob/master/docs/st...

Have you tried Reason[0] and Reason-React[1]? [0] https://reasonml.github.io/ [1] https://github.com/reasonml/reason-react

The React bindings for TS are quite good--I used them every day, and they're solid. As for a ground-up approach, the bindings for ReasonML-react show how much effort it takes to have strong functional typing for React: https://github.com/reasonml/reason-react I believe that there will be an effort to rewrite React in ReasonML in the future by core members. The goal is the leverage the power of Reason to obviate some of the weird parts of the current React internals. /shrug