6 comments

[ 6.1 ms ] story [ 30.3 ms ] thread
Seams we focus too much on theory and not enough on practical side of things.
This is an edge case of one of many libraries that attempts to make form handling simpler. It's well known that rapid rerenders of complex components is bad for performance, rendering 83 form elements every time a key is pressed is obviously not going to do well. There are ways to mitigate this (like debouncing the keypress handler), but this issue alone doesn't mean React can't handle large forms.
Use the appropriate tools for the appropriate work. React do provide the alternative to use uncontrolled form fields, which would be more appropriate to this case.
I dunno, it feels like this is a success story of "third-party redux library finds performance problems, learns and fixes said performance problems."

And yeah, third-party Redux form automation libraries feels pretty far from "React has trouble with large forms."

Flagged cause flame bait. And nothing to do with React directly.