he/him 
The thing I hate most about writing React components is how much of the correctness is down to the code patterns you use. So many places to shoot yourself in the foot. Do other "view libraries" do better?
-
Pretty sure this is a language-level concern. Flow/TS help, but we need to replace the type system before we can even start fixing this problem. I haven't committed to a solution yet but
@reasonml is my best hope so far, because of the inter-op it provides with React/JS.
It's not just a type system. React's execution model fundamentally relies on you structuring your components a certain way. I haven't used @reasonml but not clear how it doesn't have the same problems.
-
-
I'm probably forgetting something.. what fundamental constraints does React impose on the way components are structured? Are you sure those constraints couldn't be modeled with a type system?
-
One example is that you should minimise allocations inside the render function ... but that's a performance issue, not a correctness issue.
- 8 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.