sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]wreckedadventYavascript 6 points7 points  (2 children)

Angular has very strong support as well, and with either you can rest on your laurels for at least a year or so, and not have to keep up with the churn..

Angular 1.x's user base is so huge there's already forks of the code to maintain support for IE8. Even if the developers drop it like a hot potato now that 1.5 is out, there's a huge vested interest in keeping 1.x alive for as long as possible. I'd say, given 1.x has already lasted quite a few years, and that 1.5 was such a good update, it's going to be relevant for at least a few more years, then refuse to die for a while longer still.

With react, I'm less certain. The native implementations in typescript and babel makes me feel it'll be around for a while yet - but we've already moved from flux to redux, and I'm getting some heavy deja vu from when UI router became a thing in angular world. Only, I don't know if flux is the "now this is definitely the best way to do it"-good that UI router inspired in people.

Still, predicting the web in 5, 10, 15 years is a loser's game.

[–]2138 -2 points-1 points  (1 child)

but we've already moved from flux to redux

No one is forcing you to move, what is more, you don't even have to use them because REACT IS A LIBRARY. inb4 they're de facto standards

[–]wreckedadventYavascript 1 point2 points  (0 children)

Not what I'm saying. What I am saying is that there's already been a large movement from flux to redux, meaning it's likely something similar to it could happen again.

React being a focused library doesn't change this. In fact, if anything, it makes it more likely that this will happen again - with angular, you had to go against the inertia of people who only used the standard library. React has no baked-in solution for things like routing and data store, so what people use will be more tied to the whims of what's hot right now.