2 ms·

React has been around for 4 years, and - along with Angular - has been a well known "obvious" choice for building JS UIs for a reasonable period of time. At lea

React has been around for 4 years, and - along with Angular - has been a well known "obvious" choice for building JS UIs for a reasonable period of time. At least in the "mainstream". Love for Angular seems to be dwindling slightly, and VueJS is something of a rising "new kid” on the block here, though both are happening very very slowly (if at all) and React remains a strong choice. My point here is, while I definitely bemoan the "JS lib-of-the-moment" fatigue, I think this largely applies to the millions of ancillary libraries. The range of major mainstream choices for base frameworks/&c. it's pretty small, well established, and very comparable to other language communities. If the objection is to JS the language, that's maybe fair game for the likes of Electron or Cordova but for an inbuilt integrated tool for debugging JS in an app with an existing JS runtime it seems the obvious choice, no?

nxc18 9y ago
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 years ago as react is today. And now? Angular is dwindling out.
- 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.

nxc18 9y ago

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 years ago as react is today. And now? Angular is dwindling out.

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.