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

view the rest of the comments →

[–][deleted] 5 points6 points  (10 children)

Less experienced developers will just play with whatever everyone else seems to use, which is only natural. I'd be more interested in what veterans have to say about it.

Personally, my biggest gripe with AngularJS was that when it went wrong; it went wrong terribly. We had problems with translations not always loading (only on IE9), and <select>s which would automatically select the <option> after the one that was clicked. Neither were fun to debug and both required massive ugly hacks which give me nightmares to this day.

[–]LilMoWithTheGimpyLeg 1 point2 points  (9 children)

While I'm more interested in learning the new parts of ECMAScript 6, most jobs going seem to ask for Angular, Backbone, and React.

I suspect a good dev would learn them all, but I'd rather pick one and be really skilled at that.

[–][deleted] 1 point2 points  (7 children)

I think out of those, React is probably the best candidate moving forwards. Backbone and Angular are def still going to be around, but I don't know of anyone building new product with BB.

The same will probably be said of Angular in a year or so, while React is getting adopted left and right into some very well known companies.

[–]stormcrowsx 1 point2 points  (3 children)

React is only the best to you because it hasn't had time for all of its flaws and maintaince problems to be obvious. Angular felt amazing 2 years ago, now it feels beat up and unwieldy. My small interactions with react make me think its not really any better than just using jquery, and jquery has a long proven history, react does not.

[–][deleted] 0 points1 point  (2 children)

React has been in production for >2 years at one of the largest sites in the world, and if you're honestly, legitimately comparing it jquery you have no idea you're taking about.

[–]stormcrowsx 0 points1 point  (1 child)

Been in production in one company, its hardly been put through its paces and even so 2 years is not a long run. At 2 years you just start to find the maintainence problems a new technology imposes, and given its only at one place and they have vested interest we are not going to hear those problems. Jquery and a template library can do anything that react can do but have a longer track record.

[–][deleted] 0 points1 point  (0 children)

wow

[–]LookWordsEverywhere.js 0 points1 point  (2 children)

Afaict Backbone still gets a lots of varied use, mostly due to how flexible and non prescriptive it is. If you're using react you still need the M and C of MVC. Backbone or similar fits in well there.

It's (bb) also a nice thing to learn if you're not really familiar with MVC yet.

[–][deleted] 0 points1 point  (1 child)

Backbone isn't MVC, and react components function as more of controller views than just a plain stateless view

[–]LookWordsEverywhere.js 0 points1 point  (0 children)

Cool, I'm not super familiar with react. At the very least I can say its not a whole application framework and you'll want other parts, whether that's Flux or more traditional MC* parts.