> I don’t get it. Why would I need to use React if I am supposed to work on building websites?
Haven’t we established already that you need a client-side JS frameworks for managing complex interfaces? There’s a point where you website becomes so interaction-heavy you end up writing your own “React”. Until then - feel free to go with plain JS.
I felt exactly the same way. In its most generous form, the rant boils down to "well... if you know Javascript well enough, you could dispense with things like .indexOf because you could implement it yourself!" It's quite low-effort, and I don't understand how it's made its way to the front page.
I'm guessing there are lot of folks who have all sorts of frustrations with React (as there will be with any tool/service that is used by that many people), but this article is 100% devoid of any actual criticism of it, constructive or otherwise.
> I don’t get it. Why would I need to use React if I am supposed to work on building websites?
Haven’t we established already that you need a client-side JS frameworks for managing complex interfaces? There’s a point where you website becomes so interaction-heavy you end up writing your own “React”. Until then - feel free to go with plain JS.