Re:On launching AngularJS 1.2: what we learned, what we're c...
by scotth on Tuesday November 26, 2013 @06:36AM
(#6800521)
I've been deep in the docs for the past couple months, and I have never found them to be inaccurate. A bit sparse sometimes, but on the other hand the source code is very well commented. Between the two you can find your way without too much effort.
[ Parent
| on HN ]
Re:On launching AngularJS 1.2: what we learned, what we're c...
by johnbm on Tuesday November 26, 2013 @08:26AM
(#6800998)
There are two kinds of developers... those who want a single framework that will solve all their problems and which they never have to look into... and those who like to understand one or more abstraction levels below where they're actually working.
Digging into a framework's source code is natural to the latter group, but utterly alien to the former.
Documentation written for the latter group describes mechanisms, design principles, APIs, etc. The former group instead requires examples and step by step tutorials.
Both will call documentation terrible if it doesn't conform to their expectations.
Re:On launching AngularJS 1.2: what we learned, what we're c...
by cheshire137 on Tuesday November 26, 2013 @09:40AM
(#6801487)
You described that nicely. I didn't realize there was such a split, but I'm definitely of the former group. Ugh, I just want to write my own cool stuff and understand it. If I wanted to write and understand the inner workings of AngularJS, that's what I'd be doing.