61–70 of 85 posts
> and AngularJS has only been around for a few years, while jQuery, almost a couple of decades.
jQuery was released in 2006. Unless my math fails me, that is less than a couple of decades.
Opinion is valid and he wrote an article, which is more than most have done, but some factual discrepancies. The whole # of google results factoid is off as well - http://www.google.com/trends/explore#q=angular%20sucks%2C%20...
JQuery does things in a very standard way, and has been the go-to tool for developers for years. Devs grow up on it, get used to it and find it difficult to fit new ways of working into their mental model. It's like shifting from procedural to functional: the concepts are a alien and because they don't fit & there's a psychological block to learning it.
Not sure that dooms it to failure... maybe to adoption by the masses.
When you write in AngularJS, you forget the nitty-gritty DOM manipulation, you just care about your data. AngularJS changes DOM for you. A Controller holds the data. AngularJS keeps the view updated with the data in the controller. You need to fetch data from somewhere such as REST API? Just ask for it, AngularJS gives you $resource. Just like that. No initialization, handling dependencies. Feeling there's code bloat in your controller? Extract a service and AngularJS will make it singleton for you and pass it whenever you need! Need to filter data before displaying it? Write a filter! Directives are bit difficult, I understand, but all the rest of stuff is easy and very intuitive.
Microsoft folks have been writing MVVM apps in WPF and Silverlight for nearly a decade now, writing their own DelegateCommand, using an IoC container, using an ORM and plugging all these things together. AngularJS gives you all of these as one framework! (considering $resource as the ORM). AngularJS got SPA right and IMO, is the way to build apps. I don't think it'll fail.
It's not because google guys are less smart but they are in a very different working environment than `modern startup`. In today's startup, developers are designers. We don't have money to hire graphic folks, UX specialists. We learn by coding, therefore the feeling of having control is essential. The popular MVC/MVM model is used to maintain flexibility and separation of concerns, not to dispatch work to different people. The AngularJS framework gives me the impression that the developers desperately want to hand the sh*tty html/css parts to someone else as if it's necessary evil. AngularJS projects are difficult to control since by its nature, users of the framework are encouraged to let go something that are essential to the control freaks.
Are you a AngularJS advocate and a corp dev?
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'…
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.
There are few cases where I want such a thing (like say updating the count on a shopping cart when an item is added). I don't ever want an item you're adding in a form to be showing up as you type it in a list in the background. That adds nothing and on the whole it's probably a UX negative effect.
I think it's brought up so much mostly because it's cool tech. But I don't see it actually solving problems.
MS had the same tech, with an arguably simpler implementation, years ago in ASP.NET. And while I've been out of MS development for awhile I feel like it's been largely deprecated. And it was never a "best practice" in the first place. It was mostly just a demo tool for MS sponsored "conferences" (read sales demonstrations by MS employees who went on to found Telligent).
When I am struggling with "agh why do I have to do it like that" in either framework I later find that either 1) the difficulty was necessary for some important reason and they're saving future me from easy mistakes or 2) that the difficulty was due to me not knowing some really amazing concept or paradigm or pattern.
This isn't to say that angular is perfect, but damned if it isn't elegant, powerful, and well thought out.
I've found angular to be by and large incredibly intuitive and easy to use. But there is also an effect of they're solving pains I've had in prior projects, and using concepts I'm familiar with.
Personally I find the angular concept easy to follow with the only hard part "how do I accomplish X" which is pretty easy to find answers for.
Earlier quoted context omitted.
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.
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'.
Not saying that represents the market, but just saying it's taken off in my corner of the world significantly.
We 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.
Simpler, yes, but simplicity often comes at the expense of power. What happens in a year, when you have a bunch of experienced developers, struggling to overcome the limitations of ReactJS? Most likely you'll end up reinventing many of the things that Angular provides out of the box. It is always tempting to take short-term gains over long-term costs, and in some situations, it may be the right thing to do. A company…
Trading simplicity for power is a false dilemma. If there's any library on the web that demonstrates this, it has to be React.
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 struggle…
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…