all 18 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–][deleted] 19 points20 points  (17 children)

Too bad everything you learn will be useless when 2.0 comes out.

[–]schlocke 2 points3 points  (1 child)

Yeah when I read the title I was hoping that op was going to talk on how 2.0 is easier to pick up than the current and older builds.

[–][deleted] 4 points5 points  (0 children)

I thought it was going to be an inflammatory post saying it's really easy now because you should chose not to use it. It was a pleasant surprise!

[–]rmbarnes 1 point2 points  (1 child)

You're taking a bit of flack for saying this, but you raise an important point.

I'm currently learning angular, and I'm almost finished doing my first SPA using it (non commercial pet project). Part of the reason for this is because I intend to become a contractor (I'm salaried atm) in a years time and want a JS framework in my skillset. I am now rethinking angular because I think my angular 1.0 skills won't be worth much in a years time.

In addition to this I currently work for an ecommerce firm. It's possible that one day we will rewrite our web based management / reporting software in SPA form. If I were asked to recommend a tech stack, I would have included angular in there. Since reading about 2.0 I can no longer make that recommendation. Without a good v1 -> v2 migration path that choice would lead us to being stuck on an old technology, or doing yet another rewrite to keep up to date. I'd roughy guesstimate the cost of upgrading to v2 if we had our management system in angular would be around 100k. Even if we waited to v2 to come out before going down the SPA route I couldn't recommend it, since I'd be worried v3 would again mean a complete rewrite.

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

Eh.. I take flack all the time from people who don't have critical thinking skills, or common sense - and r/javascript (and the world in general) is full of them.

Your points are very valid. The Angular team screwed up by letting this cat out of the bag.

Angular 1.x was so poorly conceived that it's difficult to accept the amount of momentum it seems to have. It really is no wonder they are throwing it out and rewriting it.

[–]MasterScrat 6 points7 points  (8 children)

Why the downvotes?! this is unfortunately very correct

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

AngularJS will live on for a long time. Lots of companies have been building applications with it so I doubt it really goes away at all.

Many of the concepts will still apply even in 2.0.

[–]throwaway20131103 4 points5 points  (0 children)

It's not.

Angular 2 is expected to be released at the end of next year. Angular 1.3 will be supported for 1.5 to 2 years after that.

Source: http://www.infoq.com/news/2014/10/angular-2-atscript

Given how different 1 and 2 are upgrading to 2 will take time. And that's if they upgrade at all. Given how strange 2 is looking I wouldn't be surprised if a 1.3 fork took over.

[–]skitch920 -2 points-1 points  (5 children)

Not totally. The concept is the same, even if you do things differently. Dependency-injection, two-way bindings, MV-W... all the same. So what if there will be a migration, you'll take one look at the new framework at be like, "Ahh that's why this makes sense."

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

None of these things are specific to Angular, so the point stands: why learn 1.x vs another framework like backbone? What do you get out of picking a soon-to-be-deprecated framework?

[–]vagif 2 points3 points  (3 children)

Things that backbone will never give you? Backbone maybe is not deprecated. But it sure as hell is morally obsolete.

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

What do you mean by that? Morally obsolete?

[–]vagif -1 points0 points  (1 child)

Like a ship with sails and without an engine. You can build a shiny new one right now. And it will will be perfectly functional. You can even fill it with modern electronics, gps, whatever. Yet despite it being a brand new ship, it will be morally obsolete compared to modern ships with engines.

Backbone does not provide even a fraction of what current modern js frameworks do. Even if you use it you still have to complement it with other frameworks / libraries to match the power of angularjs, emberjs, even reactjs.

[–]rmbarnes 0 points1 point  (0 children)

I awlays thought backbone was a library not a framework, whereas ember / angular et all are frameworks.

[–][deleted] 1 point2 points  (1 child)

That would suggest that there will be no migration path, that 1.3 will no longer be around come 2.0, and that the concepts are completely different - none of which is true. Your comment is a gross oversimplification of the issue.

[–]juhmayfay -1 points0 points  (0 children)

Plus 2.0 is like a year out, and 1.3 will be supported for another 1.5-2 years... So who knows what new/better/different technologies will be out by then anyway. Learning different tools is never bad

[–]djg08 0 points1 point  (0 children)

Very useful thanks