Personally, I wouldn't call 1.3 deprecated until it has an official end-of-support announcement. At ng-europe, the claim was about a year and half of support for 1.3 from the angular team after the official 2.0 launch. Once there's an official announcement to the effect of "the angular team will not be supporting 1.3 after this date", I'd call it deprecated.
I do agree that most ng books run the risk of being outdated as they go to press. Quite a few resources on the web are also outdated; there's a lot of 1.0-era documentation that's not necessarily *wrong*, but certainly isn't what I'd call best-practices. Take $http for example. How many people use $http().success instead of .then chains? I've seen a few people even use the .success route to manually construct and return a $q deferred object so they can use .then on the return value. I also agree that it's worth looking at other frameworks as well. I did quite a bit of work building an ember and angular prototype for the project I'm on now, trying to see which fit better. Nowadays, I'd also look closely at react-flux. That in particular seems like a really solid contender for the small-project space. e On Wed Nov 12 2014 at 8:05:00 AM Anton Trapp <[email protected]> wrote: > *Agree* (Except the claim that 1.3 is deprecated) I just find it a little > bit unfair to hide important information. Mark most 1.x methods deprecated > and everybody will see what's going on at first sight ;) > If you claim that 1.x is not deprecated when 2.0 comes out we have > different ideas of deprecation ("that it should be avoided (often because > it is being superseded)" - wikipedia). The first internet explorer is not > deprecated, because you can (theoretically) still use it? Nice idea ;) > > And especially for people who start learning: there are other frameworks > (and I am sure that some people will consider using ember, meteor, Angular > 2.0, ... if they have the information) and even when one sticks with 1.x (I > will, because I think and hope that the migration effort in 1-2 years will > be less than trowing all away I already did) it is important to know these > facts too (if you have a paying customer and must calculate your efforts). > > *My error*: Maybe I should start with: "*If you are just curious about > the framework, resources would be - because AngularJS is one of the best > frameworks....* - if you need to go to production until... and not with > the "wast for most", maybe people who call me a troll would then read the > whole post before answering ;) > I don't want to scare away all people, for some Angular 1.x *could* > *still* be the best decision. > > But - for example - I can't recomment the AngularJS in Depth or AngularJS > in Actino MEAP books (I would have before the 2.0 "announcement"). David & > Jason Aden, Brian Ford and Lukas Ruebbelke started a great job! But how > motivated will they be to put effort in those books for the next year to > finish MEAP when the framework is deprecated and earn money with impressive > good books that won't sell? How motivated will people be to buy books about > a framework that possible won't be finished at all? > > And if itshould be AngularJS - I was happy with "The Complete Book on > AngularJS" as kind of reference and "Mastering Web Application Development > with AngularJS" - not at 1.3, but the most important things for a long > weekend :) > > Am Mittwoch, 12. November 2014 16:42:56 UTC+1 schrieb Eric Eslinger: > >> Hyperbolic claims about 1.3 being deprecated are a long way from being >> helpful. If you want to write software that lasts forever, I suggest Cobol >> or Fortran. On the other hand, if you want to write web software that will >> run on modern browsers for quite some time, angular 1.3 will continue to >> function for quite some time (measured in years). If you want to wait to >> have a framework that's got some guarantee of LTS, well, that's fine with >> me. >> > -- > You received this message because you are subscribed to the Google Groups > "AngularJS" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/angular. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
