21–30 of 85 posts
Try to build the kind of apps you can build with angular in a few days with jquery and you will see what mess you end up with.
I agree with the premise but disagree with the argument. > Which brings me to the pattern of ever failing technologies. Remember Moo Tools? Prototype? ... Prototype and moo tools tried to be innovative, but they just made things harder. Not only were they not intuitive to use, but referring to the documentation was even worse. Would take hours what jQuery could accomplish in mere minutes. That's just not true. I can'…
def split: scala.Seq[Task[Combiner[S, That], FlatMap[S, That]]]
you kinda scratch your head. But once you understand whats happening it doesnt feel so intimidating. I think technologies that have a good long term benefit, but a difficult upfront learning curve tend to get this kind of reaction. I think Angular is a brilliant framework and makes coding in javascript enjoyable. Yes, I had to read 10 articles before I understood what the hell transclusion was, but once you invest a little time learning, it doesnt feel so bad.
I'm glad good scientists don't stop studying something because it's difficult, it would have sucked for quantum theory.
Seriously, though, that's the argument? A technology will fail because it's difficult? Hopefully the OP meant "overcomplicated" or "I tried to learn it and it was beyond my ability", but saying that something will fail because it's difficult is just stupid.
Besides, even if Angular were to fail overnight, right now. The download sites go dark, the team is disbanded and starts working on something else, I'd argue that Angular has already succeeded by showing everyone a new way to tackle single apps and how to structure Javascript applications.
Having said that, I'm pretty sure Angular is going to be around for quite a while.
I agree with the premise but disagree with the argument. > Which brings me to the pattern of ever failing technologies. Remember Moo Tools? Prototype? ... Prototype and moo tools tried to be innovative, but they just made things harder. Not only were they not intuitive to use, but referring to the documentation was even worse. Would take hours what jQuery could accomplish in mere minutes. That's just not true. I can'…
Custom Elements + Two-way Data Binding + Services seems to be a pretty powerful combination.
A tool doesn't fail because it's difficult, it fails if its difficulty is not worth the results it produces. A chainsaw is more difficult than a plain old saw. You gotta make sure it's fueled up, oiled and whatnot. You might even have to read instructions the first time! But is it worth it? That's the question, and it goes completely unaddressed in this post.
Coming off working on a large Backbone app, I've seen how bloated, needlessly repeated, and painstakingly verbose things can get. Angular solves a lot of the problems I have with Backbone by taking care of basic plumbing for me so I can focus on the unique parts of my app. It's magical, but that's what I want in a framework: less pounding out boilerplate and more writing application code.