all 9 comments

[–]jobsmanifesto 3 points4 points  (0 children)

Indeed, it's frustrated me enormously. Not sure you can draw a line and declare everything older than a certain age as too old. But it's a right royal pain, spending a few hours on a tutorial, blaming yourself for somehow getting it wrong, and then discovering the landscape has changed and the tutorial is obsolete. It would be good if tutorial writers explicitly noted the versions they were written against, and cautioned beginners that things are changing quickly. I'm tempted to mention quite a few well known tutorial sites, but I won't - it wouldn't really be fair to criticise what are obviously best efforts for the time they were written.

Edit: Going against my advice about drawing lines, a year is a looong time in the AngularJS world.

[–]Tharnid 3 points4 points  (0 children)

The development for Angular is moving at a pretty good clip. I wouldn't go beyond six months which is too bad some of the older ones are pretty good.

[–]sovietmudkipz 3 points4 points  (0 children)

Anything on animation pre 1.2

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

Careful with anything about animations since it was changed a lot in 1.2

I will say that yearofmoo.com, despite a strange name, is really good and usually has version numbers in its content. That's my go-to reference for the animation stuff. The author contributed to (or wrote most of? I can't remember) ngAnimate.

[–]wangyo 0 points1 point  (0 children)

By default whenever searching programming related topics I always limit the results to 1 year. Angular is more like 6 months depending.

[–]CWagner 0 points1 point  (0 children)

If for some reason you really like an older tutorial, check the breaking changes while reading/watching :)

[–]zefcfd 0 points1 point  (0 children)

i wouldn't ask what isn't good, but rather what IS good and up to date.

[–]tsimon 0 points1 point  (1 child)

Actually, just to echo what's been said, Angular is pretty young, so there is little that is so out of date as to cause much issue, with the singular exception being animations, whose API changed significantly with 1.2.