I think the author is right, if Angular stays how it is today. I've spent a lot of time trying to learn and believe in Angular. I've failed to be persuaded that it's the end-all, be-all that many people think it is. Nothing I've read--not the docs, nor ng-book--have successfully given me the mental model for what the heck is going on behind the scenes. I think directives are a horrible hacky mess. I recently struggled mightily to design a simple recursive tree directive. Apparently it can't be done without hacking the compile/link plumbing [1].
But my understanding is that Angular is actually going to vastly simplify and modularize in version 2 [2]. I've read that Web Components will be replacing directives [3]. Notably Google is also sponsoring Polymer, which is based on Web Components. Object.observe is going to vastly simplify the scope situation.
You've further reinforced my gut feeling of staying away from Angular at the time.
I'm a data guy, and I only mess with web apps to present my stuff. Recently I wanted to do a realtime map app to display tweets processed by some ML stuff I had built.
I started to look at Angular, got a headache, and then built it with Meteor. It was ridiculously, almost embarrassingly easy. I felt like it was 1996 and I was sneakily using Microsoft Frontpage to build my web page instead of hand coding it.
Now, I'm not an idiot. I understand that Angular is a toolkit for building things which are much, much bigger and more complex than anything I touch. But if they can make it easier with version 2, I'll wait until then.
Comments
I think the author is right, if Angular stays how it is today. I've spent a lot of time trying to learn and believe in Angular. I've failed to be persuaded that it's the end-all, be-all that many people think it is. Nothing I've read--not the docs, nor ng-book--have successfully given me the mental model for what the heck is going on behind the scenes. I think directives are a horrible hacky mess. I recently struggled mightily to design a simple recursive tree directive. Apparently it can't be done without hacking the compile/link plumbing [1].
But my understanding is that Angular is actually going to vastly simplify and modularize in version 2 [2]. I've read that Web Components will be replacing directives [3]. Notably Google is also sponsoring Polymer, which is based on Web Components. Object.observe is going to vastly simplify the scope situation.
[1] http://stackoverflow.com/questions/14430655/recursion-in-ang...
[2] http://blog.angularjs.org/2014/03/angular-20.html
[3] http://stackoverflow.com/questions/18089075/what-is-the-diff...
You've further reinforced my gut feeling of staying away from Angular at the time.
I'm a data guy, and I only mess with web apps to present my stuff. Recently I wanted to do a realtime map app to display tweets processed by some ML stuff I had built.
I started to look at Angular, got a headache, and then built it with Meteor. It was ridiculously, almost embarrassingly easy. I felt like it was 1996 and I was sneakily using Microsoft Frontpage to build my web page instead of hand coding it.
Now, I'm not an idiot. I understand that Angular is a toolkit for building things which are much, much bigger and more complex than anything I touch. But if they can make it easier with version 2, I'll wait until then.
if it's for personal projects maybe vuejs will be better for you than angular. same principles, much simpler execution.