4 ms·
the author actually has a series of "Angular Bad" articles on his blog which are more or less specific: http://www.fse.guru/angular-bad-parts-part-1 http://www
by itomatik 12y ago
the author actually has a series of "Angular Bad" articles on his blog which are more or less specific:
http://www.fse.guru/angular-bad-parts-part-1 http://www.fse.guru/angular-bad-parts-part-1
http://www.fse.guru/angular-bad-parts-part-2 http://www.fse.guru/angular-bad-parts-part-2
http://www.fse.guru/angular-bad-parts-part-3 http://www.fse.guru/angular-bad-parts-part-3
http://www.fse.guru/angular-bad-parts-part-4 http://www.fse.guru/angular-bad-parts-part-4
http://www.fse.guru/angular-bad-parts-part-5 http://www.fse.guru/angular-bad-parts-part-5
http://www.fse.guru/angular-bad-parts-part-6 http://www.fse.guru/angular-bad-parts-part-6
- kfnn 12y agoTo me it's not specific enough. In the first part the author claims that >'Dependency injection lacks some functionality you will need sometime.' But fails to reveal which functionality he has in mind. He later claims that 'inheritance is an antipattern' and posts a link to google search results as 'proof'. Not worth reading, in my opinion.
- deleted 12y ago[deleted]
- xpto123 12y agoIf we boil this down it says: its a huge framework. it works but there is a big learning curve, and there are pitfalls. You might run into performance problems, you will need experienced people, you will have to know a lot about the inner workings of the framework to pull a big project off. This could be said about any big framework: Spring, Hibernate, GWT, JSF the list goes on. The conclusion of the author: because of this its not good enough and I don't recommend it. But he is right about the bad parts, those are basically the reasons why Angular 2 will not be backwards compatible, although a migration will exist.