1. It's not. React has had classes and states from the very begining. In fact, purely functional only views came in React 0.14.
2. That said, it really does make coding, debugging, and reasoning about views so much easier. When I have a bug in my React/Redux app, I can look at the Redux state, and figure out the cause of the bug right then and there. I'm not looking for some variable that accidentally got changed five steps ago.
My bug is either in:
(a) How I went from application state n-1 to n, or
(b) How my current application state is rendered in my views
Both of these are very fixable.
...of course, I do also have stateful React views in my app, and code with side-effects, because being "pure" all the time isn't always practical. If the bug is in those places, I'm in for a much longer debug.
1. It's not. React has had classes and states from the very begining. In fact, purely functional only views came in React 0.14.
2. That said, it really does make coding, debugging, and reasoning about views so much easier. When I have a bug in my React/Redux app, I can look at the Redux state, and figure out the cause of the bug right then and there. I'm not looking for some variable that accidentally got changed five steps ago.
My bug is either in:
(a) How I went from application state n-1 to n, or
(b) How my current application state is rendered in my views
Both of these are very fixable.
...of course, I do also have stateful React views in my app, and code with side-effects, because being "pure" all the time isn't always practical. If the bug is in those places, I'm in for a much longer debug.