4 ms·
My first thought was exactly this -- a re-invention of the original AngularJS, which aimed to combine elements of scripting with HTML. I was attracted to the or
by rexreed 5y ago
My first thought was exactly this -- a re-invention of the original AngularJS, which aimed to combine elements of scripting with HTML. I was attracted to the original AngularJS, but not so much the later "Angular".
- ipaddr 5y agoWould love to see an insiders view on what killed angularjs. Technically there were limitations with that approach but by that point that had such marketshare. Did they consider that everyone would flee or did they feel like the developers would just be pulled along?
- shrew 5y agoAs far as I've seen, what killed it was the issue that Angular "v2" was so different from Angular.js (v1) that the upgrade path simply wasn't there. Eventually an upgrade path emerged where a page ran both a bulky Angular.js app AND an Angular v2 app, but it wasn't good enough. By then, React (and to a lesser extent Vue) were looking far more interesting so many teams made the decision that if they had to rewrite their app, they may as well write it in something that has a large community around it and was seen as the "latest and greatest". It's a shame as I liked a lot of Angular.js but it still lags behind in size and performance these days so it's only attractive to teams that know they're making large, heavyweight web-based software from the start.
- ipaddr 5y agoI still like it myself the 1.x branch. The latest AngularJS version I used was 4 and the boilerplate was heavy. Without an upgrade path I wondered why they didn't wait.