7 ms·
I've used it on a lot of client projects, my current one included. Angular's batteries-included approach makes it way faster to spin up a new app for a new proj
by maxfurman 4y ago
I've used it on a lot of client projects, my current one included. Angular's batteries-included approach makes it way faster to spin up a new app for a new project, and avoids the problem of picking the wrong dependency for (state/navigation/styling/etc.) that plagues React projects.
- WinstonSmith84 4y agoNext.js has finally solved React's mess But I can't agree more, Angular has for its whole existence of 10+ years always been more consistent. But it's not always about tech - Facebook's Marketing > Google's Marketing ...
- pavlov 4y agoGood marketing in this space is also about leading by example and eating your dog food. Facebook used React internally before releasing it. Every new web front-end at Meta is written in React. They also had a convincing story of how the runtime expands beyond the web (React Native etc.) With Angular, you’d be hard-pressed to name a Google service built using it. It seems to be a framework created condescendingly for the ordinary others, not the Mountain View geniuses themselves. That’s not great marketing.
- WorldMaker 4y agoThe Google Cloud Console is the most notable Google service built with Angular and my experience is that's one of the best advertisements for not using Angular. If even Google engineers theoretically just offices away from the Angular team can't make a performant Angular app, who can? The Angular Team act like it's a great feature that they don't give "special" support to in-house dogfooding teams, but that just leaves as much an impression that they'd rather just support everyone equally bad. Sure "no special support" sounds great on paper, but it certainly looks like "no support at all" from where I'm standing. Some Angular proponents will also make excuses that the Google Cloud Console is an amalgamation of components and pages owned by a variety of different teams, like that's a unique situation to Google that no one else deals with bureaucratic scale like that. I guess they haven't experienced much other enterprise development, because that is very common in my experience. If they aren't building Angular for multi-team enterprise applications, what exactly are they building it for? (They are certainly advertising Angular as great for those, even if they are using it as an excuse for why Angular isn't performing well in Google's own usage of Angular.)
- tashoecraft 4y agoI like how people make this jab at angular without acting like Facebooks site is so god awful. If react is so great why is the Facebook site terrible? Large companies have large company issues regardless of front end framework.
- WorldMaker 4y agoFacebook's site is awful, but performance, and specifically the performance of React on Facebook if I feel like watching profiling reports in Dev Tools, is rarely ever my complaint with Facebook's site. (When I have noticed performance issues with Facebook they were network/backend issues, not front end issues.) Facebook seem to have some pretty aggressive performance goals, meet them more often than not, and React seems to benefit well from that dogfooding (as release notes have sometimes mentioned that performance improvements were driven by Facebook's needs). Anecdotally, having to profile the performance of apps I've built on Angular and React I'd much rather be profiling a React app than Angular any day of the week. I got so frustrated with Zone.js at one point I wrote an entire "Component Framework" for Angular to avoid Zone.js as much as possible and try to remove Zone.js entirely as a dependency in Angular apps that I need to profile.
- mat0 4y agoI’m sorry but that’s just not true. You can check this page to get a pretty extensive list of Google products made with angular https://www.madewithangular.com/categories/google/ https://www.madewithangular.com/categories/google/
- avianbc 4y agoAt ng-conf like 2-3 years ago they said that they use angular for over 2000 internal projects at google.
- mhoad 4y agoIt’s ok sometimes to admit that you just don’t know rather than to make things up out of thin air.
- rhacker 4y agowe're using next, it's pretty awesome smoothing over of some of React's missing features. That being said I still love straight up React.
- woodpanel 4y agoAfter using Angular for years at large Blue Chip projects I decided to switch over to React projects to see the other side of the isle for the last 4 years. The atomicity of React makes it applicable in an immense variety of usecases, however this comes at the cost of an ecosystem providing a very fragile dependency graph. With React you'll almost always have the newest trendy thing available as a tool (and not with Angular)[1]. Which means if someone comes up with a completely new philosophy that might better match your (team's) mental models, chances are it's available for react first. OTOH this means chances are that the concensus of "how to do things" has changed so much within a short time, that older projects are not only difficult to upgrade, but consist of code that is really, really hard to understand at all. [1] e.g. there was a time when Google's own Material UI was better implemented for React than for Angular.