Why does Angular.js rock?

Post by d0m » Sun, Aug 04, 2013, 2:57 PM UTC

sahrizv wrote: post #114

d0m wrote: post #105

Earlier quoted context omitted.

I'm a django expert and I've built dozen of projects with it. So it would be hypocrite of me to tell you not to learn it. On the other hand, when I first started learning it, it was a young framework not well known (PHP was still hot.. Rails and Django developers were the hipsters of the web on the edge of technology ;-) I'm pretty happy about my choice to be on the edge as when it got mainstream, I was already very…

I understand the point you are making. The only problem with picking up a relatively less mature/complete framework is that I intend to use it in production. Since I am starting up as a novice, I cannot afford to sacrifice maturity for the high of being on the edge. I realize there's benefit for me in being on the edge as you mentioned( and I would love to play with the newest toy), but in my case, I unfortunately ca…

Post by forkhammer » Sun, Aug 04, 2013, 6:12 PM UTC

overgard wrote: post #102

forkhammer wrote: post #98

Earlier quoted context omitted.

Here's the brief answer, as I understand it: they're frameworks that provide model-view data binding, ease data/presentational decoupling, and (in some cases) provide single-page app (SPA) infrastructure in the mode of MV*. In short, they're designed to tackle some of the common complexities that arise when writing feature-rich multi-part SPAs. You can do it all on your own, for sure, and I actually think that writin…

That's just more buzzwords though. I mean, why do I even need model view data binding? I'm not saying it's not nice to have, but I've written some pretty complicated applications and I never really found data binding to be some sort of killer feature. It's generally struck me as a great demo feature that in reality I'll pretty much never use. I guess I'd find these things more convincing if they showed me some sort o…

Post by hayksaakian » Mon, Aug 05, 2013, 6:50 AM UTC

Foxandxss wrote: post #75

hayksaakian wrote: post #72

It works great but what if we want the input to have the focus when the page loads? jQuery right? We grab the input and we call the focus() method in it. NO. With directives we want our HTML to be as self-descriptive as possible so we are going to create a focus directive. Or you could use html5's autofocus http://davidwalsh.name/autofocus and cut the JS ----- Otherwise great article, I'm really leaning hard towards…

True, but the directive will reach to those places where html5 is not a welcome guest. But to be sincere, I picked one thing to a directive, there are infinite ideas but I needed one easily enough for a "hello-world" type of post.

Post by KurtMueller » Mon, Aug 05, 2013, 2:23 PM UTC

at-fates-hands wrote: post #81

oinksoft wrote: post #40

Earlier quoted context omitted.

The documentation is not impenetrable, it is just that AngularJS is a library that takes a while to get up to speed on. What is lacking right now is writing on best practices and application design. The O'Reilly book offers some of this, but generally it's just a warm-up with a couple case studies at the end. http://docs.angularjs.org/guide/concepts is a model of good documentation, and http://docs.angularjs.org/guid…

>>This is why newcomers find the learning curve steep: It is a new way to write applications. As someone who's run the gamut of "trendy" JS frameworks, I picked up Angular much faster than Backbone, Ember and Knockout combined. Maybe it's the MVC thing, I don't know, but something just clicked with me with Angular. After watching a few tutorials, I able to build something from scratch without much effort.