Bingo. That is kind of my benchmark of "should I use this?". If code is too arcane and hard to understand (especially when docs a slightly lacking) I usually pass it up.
It could reflect on my density and stupidity (can't read code too well) but so far I've had good track record.
I tried understanding and learning Angular.js but got lost in directives, dollar-sign prefixed identifiers, services and other custom terminology.
One way to make sense of it is to look at the source, and that was pretty painful.
Anyway so far it fails my smell test so I'll pass it up. Maybe later will revisit.
Very good point. The terminology is exactly the thing that's (in my opinion) is weird with Angular.
When I had a first glance on it, I didn't really get it. Only after several hours reading the docs and experimenting with code I got what they were talking about things became somehow clear (lots of aha-moments "ahh, the service is just a fancy name for an angular-managed singleton, now I see...").
It could reflect on my density and stupidity (can't read code too well) but so far I've had good track record.
I tried understanding and learning Angular.js but got lost in directives, dollar-sign prefixed identifiers, services and other custom terminology.
One way to make sense of it is to look at the source, and that was pretty painful.
Anyway so far it fails my smell test so I'll pass it up. Maybe later will revisit.