I disagree. I found the tutorial for beginners really well done and when followed by the conceptual model it was solid.
We're thinking of integrating them into our course at http://www.thinkful.com/ – though we provide more structure than just the docs, they're pretty solid on their own.
I actually started with Backbone and found the documentation sketchy. Nearly every tutorial had a different configuration than the last one. Backbone and Rails, Backbone, Ember and Mongo, Backbone and Coffeescript.
Nearly every one of the Angular tutorials was concise, took the same approach and used the entire framework, without any other dependencies. This made it easy to learn dig in and get going. In the few weeks I've been learning Angular, I've already built two CRUD apps and a pretty sophisticated navigation with it.
It just feels like a full fledged framework, as opposed to just a useful library.
After the tutorial I went off and built something that wasn't, based on my current understanding, a "proper" Angular app (paging all True Scotsmen).
These videos for example showed me that creating directives is actually a central thing you do in Angular. Not just a neat thing you can do occasionally.
I actually started with Backbone and found the documentation sketchy. Nearly every tutorial had a different configuration than the last one. Backbone and Rails, Backbone, Ember and Mongo, Backbone and Coffeescript.
Nearly every one of the Angular tutorials was concise, took the same approach and used the entire framework, without any other dependencies. This made it easy to learn dig in and get going. In the few weeks I've been learning Angular, I've already built two CRUD apps and a pretty sophisticated navigation with it.
It just feels like a full fledged framework, as opposed to just a useful library.