Where React JS is strong
React is based on building components, which forces you to write reusable code. This is great for all of us lazy developers who tend to just copy, paste and change stuff whenever we need features we’ve made before. It can even take care of user interaction in an easy, straightforward manner. But it’s not all glitter and unicorns, as with all things, React has its dark side.
That’s it for an overview of React, but what about Angular ?
What Angular JS does best
But, again, it’s not always sunny in Angular.
The blunt angles
As with most frameworks, Angular struggles with huge data sets. It does so because it’s designed to have two way data binding. That means it knows when data has changed in any part of the structure and reacts accordingly. The problem is, to find a single node where data has changed, it has to loop over the whole set. That’s not a problem with small data sets, but when the numbers get higher, performance takes a hit.
Another thing that some people find ugly about Angular, is the fact that it forces a lot of stuff you may not need. It bundles a lot of functionalities that you may never use, and that’s not really what you want.
Now, the good news is, everything can be changed.
The web is a beautiful place
Did you notice how Angular’s weakest link is exactly what React does so well ? If you did, then you’re already wondering if they can be used together. Fact is, they can. React makes no assumptions as to what framework you’re using, so in theory you can use React as the View component of your Angular MVC. I haven’t done this myself, but I’m sure you’ll find plenty of examples in the internet on how to build Angular on steroids using React. Remember, Google is your friend.