![[ERR!]](https://pbs.twimg.com/profile_images/828593972029317120/4UXq5Hmj_normal.jpg)
425 Views
For Daniel and many React devs, there is no debate. If you care about performance, you use React instead of Angular. Period. I don’t think it is quite that simple. Performance is a means to an end. The real goal is providing a great user experience. No doubt speed matters, but not all changes in speed are perceived by humans the same way.
2 comments
Dom Barker
10/15/2014 1:36:32 PM
1. Don’t create complex Angular apps. Most great user interfaces are simple. Do you really need 2,000 controls on a page?
This is yet another reason why I don't recommend using Angular. Frameworks like Angular are intended to make it 'easier' to create big (aka complex) javascript applications and yet the framework itself starts causing issues when apps get big. By the time you find out, you are already fucked.
Robert Greyling
10/15/2014 3:58:39 PM
Undoubtedly, there are a huge number of complex Angular apps that suck. So in a way given Angular makes it easier to write complex apps, you maybe right that it gives you the rope to hang yourself with. But that doesn't mean all complex Angular apps are crap or perform badly.
As you know, experienced devs know there are good ways and bad ways to build things. I think developer laziness comes into play here a lot. There's definitely evidence for large complex apps built with Angular running just fine and very performant. A lot of that is down to the dev team having used good sound proven practices.
Personally, I don't have a problem with using any framework like Angular, Durandal, Ember, Backbone, whatever - if you write good code, I think the framework will help you more than it'll hinder you, and I don't think anyone can argue that time to market is a heck of a lot faster using a framework well, than using none at all. If that wasn't the case, these frameworks wouldn't exist.