This guy is crazy to write an opinion article without examples (only the opinions) and without expertise or understanding of the history, the current solutions, and their differences.
React is bad is youre bad. Its much more fundamental than other frameworks. It also paradigms shifts from imperative to (more) functional. So if you are not comfortable with closures and side effects (like the author), you will get lost.
None of the pattern from any framework is new. Theres only so many ways to design systems, you either use callbacks, observers, or events. All have their pros and cons (where imo observers and events are inferior due to their quick branching factor in larger codebases). React gives the option to use any of these.
> It also paradigms shifts from imperative to (more) functional. So if you are not comfortable with closures and side effects (like the author), you will get lost.
I don’t think it’s that simple. I write in a functional language for my day job, yet React hooks style components still give me headaches because they are leaky abstractions where you have to know what they’re doing under the hood anyway.
This argument feels a lot like 15 years ago when C++ developers were saying C++ is bad if you’re bad. Some are probably still saying it, but its pitfalls and crippling complexity are pretty widely acknowledged at this point.
React is bad is youre bad. Its much more fundamental than other frameworks. It also paradigms shifts from imperative to (more) functional. So if you are not comfortable with closures and side effects (like the author), you will get lost.
None of the pattern from any framework is new. Theres only so many ways to design systems, you either use callbacks, observers, or events. All have their pros and cons (where imo observers and events are inferior due to their quick branching factor in larger codebases). React gives the option to use any of these.