41 ms·

It drives me crazy when I hear things like Angular4+ is better for "Large Ambitious Applications with large teams" when in reality Angular4 suffers from the sam

It drives me crazy when I hear things like Angular4+ is better for "Large Ambitious Applications with large teams" when in reality Angular4 suffers from the same slow down/performance problems as Angular 1.x. https://github.com/angular/angular/issues/14041 https://github.com/angular/angular/issues/14041 https://www.airpair.com/angularjs/posts/angularjs-performance-large-applications https://www.airpair.com/angularjs/posts/angularjs-performanc... I mean it's like they ignored all of the lessons and knowledge the industry has learned and produced a Framework that has issues built in! But I guess the Framework was designed with consulting in mind.

arcosdev 9y ago
> But I guess the Framework was designed with consulting in mind. I need a bumper sticker or T-shirt with this printed on it
deleted 9y ago
[deleted]
slmyers 9y ago
One obscure issue that ends with the comment "It's slow but I don't think it's the crippling bug I first thought it was." hardly supports a claim that " Angular4 suffers from the same slow down/performance problems as Angular 1.x."
davidjnelson 9y ago
I prefer react but angular 2 and 4 are quite good. When used with ChangeDetectionStrategy.OnPush and ngrx/store, it's great to work with. String dsl based templates are annoying after jsx though, but angular's very nice mostly batteries included approach offsets this mostly. I also feel it's much harder to get hot reloading working as there is no virtual dom in angular. It can be done, it's just more complicated.