Hello. These articles are interesting and I would love to have Marius' opinion about it. But the most important point to me is that the Angular team is now re-writing their framework almost from scratch, and breaking retro-compatibility with the current version of the framework. That would be not such a problem if we would be able to directly use the new version, but it does not support old web browsers that do not auto-upgrade (e.g. IE 10!), so we are stuck on AngularJs 1.x. This is a serious issue since we love using technologies on the long term! Guillaume

Thanks for sharing the link with critical articles regarding angular. Allthough the authors from the link (mostly) don't seem to have much experience with it. After using AngularJS the most part of the last 2 years in mixed Java/JS projects all I can say that I've come to like it. It has a really powerful abstraction in terms of data binding and as with every framework it has a learning curve to understand its limitations. Whats a big point IMO is the pretty good ecosystem of literature, an interactive home page illustrating most features by example, (could be even better though) and an active community on stackoverflow. There is especially good optional integration with bootstrap (although you wouldn't need it too much after some training) You can say its negative that they've sort of highjacked jQuery (jQLite) for DOM manipulation but this way they stay clear of dependencies. (If jQuery is loaded before angularjs it will be used instead of jQLite) On the negative side there is the uncertain future with compatibility-breaking version 2.0 on the horizon. Thats really sad as they really should'nt have named version 2 'angular'. I can imagine that version 1.x release cycle will be never ending. I don't know if history is repeating itself, I had been a big fan of the spring framework in its early versions and learned a lot from its codebase and discussions but now I feel they sort of ruin it (although without breaking compatibility at large). Besides all tech pros and cons it seems to be sort of a general dilemma: As a framework supplier if you just keep good stuff stable and only fix bugs then people won't trust you to be innovative enough and your software/framework will be losing relevance. So they try drilling deeper holes with the risk of ruining it ... Andreas Am 08.06.2015 um 12:39 schrieb vincent(a)massol.net: