Angular allows for a clear separation of concerns and it's easy to teach individuals standards (isolate dom manipulation, no global state if possible, clear techniques like promises and data binding). It's similar techniques, if not easier, than node.js. Should we assume node.js will fail because it's too difficult for the author?
The reason Angular JS will fail
31–40 of 85 posts
Re: The reason Angular JS will fail
#32We found that the Angular learning curve was steep and was difficult to bring new devs up to speed quickly.
Our solution was to migrate from Angular to ReactJS. Much simpler, faster and better.
Re: The reason Angular JS will fail
#33I think a better argument would have been not adding Angular to every project by default because it's the new hotness/shiny. There is a great use case for Angular but if all you need are some onclick's then yeah Angular is overkill and complicated. But if you need two-way binding and a semi-complicated UI then it simplifies a lot of stuff vs. straight up JQuery.
Re: The reason Angular JS will fail
#34A 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.
Minor aside, I like the chainsaw metaphor and use it a lot when thinking about programming tools and languages.
Before choosing a tool / language, I check if the task is to (metaphorically) cut a single tree or an entire patch of trees. If the answer is former, I choose an axe (a simpler tool), else I stick with the chainsaw no matter how difficult it gets, as it will pay in the long run.
Re: The reason Angular JS will fail
#35I guess vim and git will fail too.
Actually that same blogger wrote such a piece regarding git: http://okmaya.com/2014/03/10/git-kinda-sucks/
For those interested, he's also written a web framework:
http://okmaya.com/2012/08/08/successfully-completed-the-fram...
It eschews OOP, for the following reasons:
"1. Now imagine coming to a website where you have to wait even 30 seconds for every page to load because it has to build objects. Just doesn’t make any sense.
2.Why build objects on every page load, when all the objects are going to be gone once the page is loaded anyway?
3.It’s like building a stock car at the start of every race only to completely take it apart at the finish line. Pointless."
He also gives out some advice:
"Note to OOP Web Devs. Stop being lazy and learn to actually program."
Re: The reason Angular JS will fail
#36I 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'…
I wish there was more discussion of the core concepts in Angular instead of just the implementation. Custom Elements + Two-way Data Binding + Services seems to be a pretty powerful combination.
That's what I was looking for when I found Angular.
There are definitely two questions worth asking:
1) Is that combination really what we want? (I think it is)
and
2) Is Angular's approach the only right way to do it?
So far, they've got the mindshare and a serious head start.
Re: The reason Angular JS will fail
#37And here I was just looking at some jQuery and thinking that it'd be so much easier if I was working with Angular...
Re: The reason Angular JS will fail
#38This is a fundamental problem for frameworks. To be better, you have to be different. People don't like different. They do like better, though, so the design goal has to be maximize better while minimizing different.
Angular's explosive growth suggests they've done a reasonably good job of that, and will continue to increase their better:different ratio. You can't please everybody, though.
Re: The reason Angular JS will fail
#39It may have a steep learning curve, but it is also a massive jump forward in frontend web dev.
It isn't for every project, but the main project I use it on now would have been at least 10x as much jQuery style code to write. Writing code isn't hard, maintaining it is.
Re: The reason Angular JS will fail
#40Apples and oranges...Coming from a backend developer background i actually found angular pretty easy to pick up. Most of the backend frameworks are much more complex. And angularJS is to be compared with application frameworks, not with a javascript toolkit to enhance static websites like jquery. 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 w…
I have exactly the same feeling. I am mostly backend developer who started with angular this week. After few days I was able to create mvc app, thanks to the multiple plugins I was able to finish it really fast. DI and other features make it easy to maintain over time. jQuery is cool for simple frontend features, but not for maintaining complex mvc frontend.