4 ms·

I think that's kind of the point. Angular was not only the choice just a few years ago, it is still a relatively new technology. It was just as obvious a few ye

• nine_k 9y ago
  Building software in an excessively timeless way is not always a good idea. You build a major bridge once a century or more. You release software every couple of months, if not more often. You need speed and ease of change more.
• lucideer 9y ago
  I don't know if Angular is really dwindling that much; if so, it's at least doing so slowly. Even so, in terms of solid base frameworks, I think the rate of change is both reasonable, and comparable to other language ecosystems. The first major generation in the JS world was Mootools/Prototype/jQuery which started with a lot of churn, settled, and jQuery emerged as somewhat defacto. In between, we've had a minor mini-generation with a bit of Backbone, Ember and Meteor stuff happening, before this world of Angular/React/Vue. These are all changes that I think have taken significant time to come about - they're really not too​ difficult to follow. The massive daily churn of smaller add-on libs is more painful but easily avoided tbh. Similar things have happened elsewhere - PHP's ZF, Symfony, Laravel, ?, Ruby's Rails, Sinatra, Java's many many complex evolutions, &c. &c.