Simpler, yes, but simplicity often comes at the expense of power. What happens in a year, when you have a bunch of experienced developers, struggling to overcome the limitations of ReactJS? Most likely you'll end up reinventing many of the things that Angular provides out of the box.
It is always tempting to take short-term gains over long-term costs, and in some situations, it may be the right thing to do. A company that gets a product out of the door in a couple of months using ReactJS may beat a company that spends 12 months building a "better" one with AngularJS. But the reverse may happen instead: The company that adopted a simpler technology may become bogged down trying to extend beyond its limitations, giving their competitors a chance to accelerate past them.
It's the old story of the tortoise and the hare. Except, as with any fable, real life is never so clear-cut, and gains in one area will almost always be countered by losses in another.
That's a good, albeit very generic argument where you can switch Angular and React with simply A and B. My guess is that you haven't tried React? It's been in production at Facebook/Instagram for a few years now and powers the money-making parts of the site.
Trading simplicity for power is a false dilemma. If there's any library on the web that demonstrates this, it has to be React.
Comments
We found that the Angular learning curve was steep and was difficult to bring new devs up to speed quickly.
Our solution was to migrate from Angular to ReactJS. Much simpler, faster and better.
Simpler, yes, but simplicity often comes at the expense of power. What happens in a year, when you have a bunch of experienced developers, struggling to overcome the limitations of ReactJS? Most likely you'll end up reinventing many of the things that Angular provides out of the box.
It is always tempting to take short-term gains over long-term costs, and in some situations, it may be the right thing to do. A company that gets a product out of the door in a couple of months using ReactJS may beat a company that spends 12 months building a "better" one with AngularJS. But the reverse may happen instead: The company that adopted a simpler technology may become bogged down trying to extend beyond its limitations, giving their competitors a chance to accelerate past them.
It's the old story of the tortoise and the hare. Except, as with any fable, real life is never so clear-cut, and gains in one area will almost always be countered by losses in another.
That's a good, albeit very generic argument where you can switch Angular and React with simply A and B. My guess is that you haven't tried React? It's been in production at Facebook/Instagram for a few years now and powers the money-making parts of the site.
Trading simplicity for power is a false dilemma. If there's any library on the web that demonstrates this, it has to be React.
Are you using React with anything else at the moment?