4 ms·
I also have been using Angular for my entire professional developer career, which in a few days will hit 2 years. This article is pretty accurate for the most
by Bahamut 12y ago
I also have been using Angular for my entire professional developer career, which in a few days will hit 2 years.
This article is pretty accurate for the most part, although some of the minor complaints are not quite so accurate.
Performance is something to be careful about, but the Angular team has worked hard at improving it and it has improved immensely with 1.3 - optimizations such as bind once & $watchGroup and optimizations around the $digest cycle and $watch make it a huge improvement over 1.2. I want to say there is a chart floating around showing over 30% improvement.
As far as frameworks go, I believe Angular is the best we have currently. It does a lot for you without getting too opinionated in general, and some of its tooling is just flat out better than much of what you can find in the wild.
I have been experimenting with Polymer lately though with an eye towards web components - there is a lot of change coming in how we will have to structure our code. I suspect that those using React will also not be shielded from the pain of integration with ES6 and web components as well, and so I have been hesitant to recommend it in a core product. Ember claims they will make the breaking changes slower, but I also suspect that it will limit its growth as well.
Frontend seems to be rolling on as fast as ever - I don't see much of a way around everyone having to scrap their code regardless of the major library chosen for their projects. I'm hoping the pain dies down once ES6 and web components becomes the norm though.
- Cthulhu_ 12y agoI wouldn't recommend either Polymer or the current development version of Angular 2.0 for a production application just yet; Polymer leans heavily on the unfinished web components standard and other experimental and unimplemented browser features, and Angular 2.0 is still under heavy development. I also gather they're either going to use ES6-but-with-extras-because-we-can, or with AtScript, ES6-with-types-because-why-not. I can't say I agree with those motivations (and I'm sure I've got it wrong), and I quite like the more vanilla JS feel of Angular 1.x. Anyway, my point is, both of those aren't production-ready.
- Bahamut 12y agoOh, I agree about not moving to either for a major project currently, although I'm probably going to use Polymer for a small static site project I'll be starting in the next month or two - web components are supported in Chrome currently (shadow DOM and custom elements at least - not sure about the data binding part yet), and Polymer's platform.js makes it very easy to polyfill the missing functionality. I suspect Angular 2 will be the best we have once it comes out, but I also question some of the decisions made from certain perspectives. At least they're listening to the community, evaluating the feedback and suggestions, and incorporating it into their decision making though, such as the change with the HTML templates.