The reason Angular JS will fail
51–60 of 85 posts
Re: The reason Angular JS will fail
#52Earlier quoted context omitted.
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.
I keep on hearing this, but I really haven't heard of it being in any large projects other than DoubleClick. I don't know if I'd consider being used in a bunch of small hobby projects a 'head start'.
Re: The reason Angular JS will fail
#53Re: The reason Angular JS will fail
#54A 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.
The article links to another page where the author rants about why Angular sucks; the second paragraph already indicates the author is trying to do direct DOM manipulation, which is exactly what Angular tries to prevent you from doing. It's an abstraction layer (amongst other things).
tl;dr I wonder if the author ever worked on a production-sized single page application.
Re: The reason Angular JS will fail
#55If the author IS trying to build a complex single-page app, then I see absolutely no reason why jQuery would be preferable to Angular. Angular does one job and does it well. jQuery is a strong candidate for most reasons you'd ever need javascript in the browser.
Yeah, I do agree that Angular's documentation is lacking, especially compared to jQuery's docs. Also, Angular is not my personal first choice front-end UI framework. However, for CRUD application development, I care much more about Angular's holistic approach rather than being able to procedurally manipulate each DOM node and event handler as I would in jQuery.
I appreciate the author's passion and think the arguments are valid, but I also feel that this is an unconvincing apples-to-oranges comparison. In my completely honest opinion, I'm not incredibly excited about EITHER Angular or jQuery, but I am grateful for both.
Re: The reason Angular JS will fail
#56We 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
#57Re: The reason Angular JS will fail
#58Earlier quoted context omitted.
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…
We all go through the "all other software sucks, it's too complex" phase. The difference is how you handle the realization, and how you let that taste influence your own programming. Some software is necessarily complex.
Re: The reason Angular JS will fail
#59However, I usually click on them anyway. I'm ashamed of myself. :(
Re: The reason Angular JS will fail
#60Angular is actually simple once you know it. It just isn't easy to learn.
I suspect it's only difficult to people who don't make sophisticated things.