[jypepin]

I like Brad's articles, but recently it has seemed like he has struggled to migrate on React, and some recent articles have just been trying to criticise React but with bad (or false) arguments, which makes it appear just him trying to justify himself not being able to wrap his head around.

React is great, mostly for bigger web apps that do need a framework and more structure, such as an SPA with multiple team members working on it.

Just like jQuery is great to do some quick and simple dom manipulation.

I've tried both opposites; I've been on teams working on large apps in jQuery, and it's hell. And I've also used React to implement simple little things, and it's also hell (part of it for reasons Brad mentions in this article).

I don't have much experience with Vuejs but I've been using it instead of React recently, and it's refreshing indeed. Just like jQuery you can just import it with a script tag and start doing some dom manipulation and it makes the code much cleaner than jQuery.

And as others have said, jQuery is not bad - it's awesome. I guess it didn't age very well with the JS env evolving, but it's great.

[chmln]

>React is great, mostly for bigger web apps that do need a framework and more structure, such as an SPA with multiple team members working on it.

I'd argue this is bad advice. What constitutes a 'bigger' project us arbitrary, and once you build your whole app on jQuery it's expensive to migrate to React once you get just a bit 'bigger'.

Now whether or not all websites need to be React-based SPAs is a different question entirely.

[jypepin]

yeah you are right about the cost of migrating, I've been through one and it's indeed to be avoided.

I badly used "bigger". What I meant was more in the lines of React is great to build what we could call web apps - something with complex logic, etc. While jQuery is better for simple DOM manipulation.

Maybe a good line is, as soon as you find yourself manipulating data you might want to think about using a framework such as React.