← provenstack.org · framework

Angular

92 engineers on Hacker News describe using Angular first-hand: 16 endorse it, 23 regret it, 8 are mixed.

44%trust
92first-hand users
76in production
endorse 16mixed 8regret 23uses, no opinion

“so i default to .NET + angular as it keeps my game open.”

endorse · production · rednb · 2026-08-29 · source ↗ · wrong label?

“I'd pushed Angular over React for a massive project, and it worked well, but the migration to Angular 2 when it came created a huge amount of non-value-adding work.”

mixed · production · bartread · 2025-12-04 · source ↗ · wrong label?

“Angular has been even more stable since the switch to TS.”

endorse · production · devjab · 2024-10-26 · source ↗ · wrong label?

“Angular 2 was effectively a complete rewrite - cleverly using the same name, thereby making it even more difficult for us”

regret · production · doctor_eval · 2024-05-30 · source ↗ · wrong label?

“leaving slag heaps of angular 1 and early dot net abandonware, years of work dumped because dependencies and frameworks were out of support.”

regret · production · monkeycantype · 2023-04-25 · source ↗ · wrong label?

“This is the one and only framework we use, monoculture. No pain what so ever with migrating from Angular version to version.”

endorse · production · _the_inflator · 2022-12-10 · source ↗ · wrong label?

“we migrated to Angular 1, it was another big win in productivity.”

endorse · production · ggregoire · 2022-09-09 · source ↗ · wrong label?

“the only ones to break a 8/10 rating among 500+ users are based on angular, react, electron or vue.”

regret · production · moksly · 2021-09-09 · source ↗ · wrong label?

“The way Angular separates concerns for us is great. And the components are extremely flexible and reactive and useful for iteration.”

endorse · production · ourcat · 2021-01-22 · source ↗ · wrong label?

“The transition from Angular 1=>2 made it clear to us that this was not a good framework to use for long-term projects.”

regret · production · bob1029 · 2020-11-12 · source ↗ · wrong label?

“Our app went from 3.5 MB to 2.3 MB when we switched to Ivy.”

endorse · production · pseudobry · 2020-11-12 · source ↗ · wrong label?

“It was fun and enjoyed it but the investment wasn't really worth it”

mixed · production · 0.33 yr · tartoran · 2020-10-29 · source ↗ · wrong label?

“I remember breaking powerbi.com due to missing > in an angular template that ended up in prod. It was a hard lesson that day never to touch untyped string based templates ever again.”

regret · production · nojvek · 2020-08-07 · source ↗ · wrong label?

“my team and I have rewritten a hard to maintain 50kloc+ angular application to elm”

regret · production · whiletruu · 2020-04-09 · source ↗ · wrong label?

“any variable created in the template itself was defined as `any`... Agreed, this is an awful default”

mixed · production · buu700 · 2019-12-19 · source ↗ · wrong label?

“we moved to embracing core framework tooling like in Ionic 4 with Angular, where you don't need to go through our custom Angular build tooling”

endorse · production · yesimahuman · 2019-10-15 · source ↗ · wrong label?

“Zero dev fucktitude (once we ditched Angular, but that is another story).”

regret · production · majkinetor · 2019-05-06 · source ↗ · wrong label?

“I switched because of the whole mess with Angular 2.x planned lacked of backwards compatibility. It was the nail in the coffin for Angular for me.”

regret · production · throwaway2016a · 2018-01-11 · source ↗ · wrong label?

“I use it in prod since 1 year yes. Angular is totally ready to be use in prod since a long time now.”

endorse · production · 1 yr · dehef · 2018-01-10 · source ↗ · wrong label?

“We've been using (leveraging like crazy!) the Angular forms system.”

endorse · production · kylecordes · 2017-12-07 · source ↗ · wrong label?

“as someone using Angular in production I'd urge you to stay far away from Angular and TypeScript.”

regret · production · ChristianBundy · 2017-12-07 · source ↗ · wrong label?

“I upgraded multiple applications at work without changing code.”

endorse · production · mcescalante · 2017-12-01 · source ↗ · wrong label?

“In my day work we're using Angular 2 (Angular 4 technically)... backward compatibility is crazy non-existant.”

regret · production · hamstercat · 2017-11-18 · source ↗ · wrong label?

“Bundle sizes after all this were unacceptably high. The documentation and talks had discussed things like tree shaking... It was not a fun experience.”

regret · production · fareesh · 2017-11-01 · source ↗ · wrong label?

“I use AngularJS/Angular and Ionic/Ionic 3 daily and I can truly recommend both Angular and Ionic 3.”

endorse · production · danieka · 2017-10-04 · source ↗ · wrong label?

“I have 4.5 years of experience in the Angular ecosystem, including in open source... Angular is much better than Ember”

endorse · production · 4.5 yr · Bahamut · 2017-08-19 · source ↗ · wrong label?

“I tried using Angular but right off the bat, I had to install hundreds of dependencies via NPM.”

regret · personal · conradk · 2016-12-11 · source ↗ · wrong label?

“The angular site takes >800ms to load from localhost, not counting the delay before it starts displaying”

regret · personal · candiodari · 2016-12-02 · source ↗ · wrong label?

“we had enough of wrapping everything in $timeout and started looking at alternatives.”

regret · production · teniutza · 2016-10-21 · source ↗ · wrong label?

“I've done large apps in Angular (which nearly made me regret choosing programming as a profession)”

regret · production · rlander · 2016-09-30 · source ↗ · wrong label?

“so far it's been great... The betas have been somewhat painful with bugs and breaking changes”

mixed · production · mattetti · 2016-05-03 · source ↗ · wrong label?

“We're moving all our Angular code to React/Redux. Angular 2.0 seemed quite a bit more convoluted than React”

regret · production · merpnderp · 2016-03-01 · source ↗ · wrong label?

“an entirely Angular-based UI (so no silly mistakes like untrusted user input in jQuery selectors”

endorse · production · buu700 · 2016-01-23 · source ↗ · wrong label?

“We next switched things to do more on the client and ran an Angular SPA app. Again we saw benefits of course, but still things sometimes were slower”

mixed · production · optionalparens · 2015-11-01 · source ↗ · wrong label?

“In Angular, it's difficult to share state between controllers. It's outstandingly slow in that it redraws far too often.”

regret · production · jamra · 2015-07-09 · source ↗ · wrong label?

“I tried Firebase + Angular and liked it well enough”

endorse · personal · rezistik · 2015-07-01 · source ↗ · wrong label?

“Testing react is very nice, especially coming from angular where testing directives was very painful.”

regret · production · TheAceOfHearts · 2015-06-21 · source ↗ · wrong label?

“we've run far away from Angular for similar reasons.”

regret · production · btown · 2014-12-20 · source ↗ · wrong label?

“I spent a year with Angular and I found it suffered from a good many issues. It is slow. It is bulky. It does too much.”

regret · production · 1 yr · williamcotton · 2014-12-17 · source ↗ · wrong label?

“Still I had to try angular for a day to really see how terrible it was in practice.”

regret · personal · nutate · 2014-11-24 · source ↗ · wrong label?

“I have been using Angular for my entire professional developer career, which in a few days will hit 2 years.”

endorse · production · 2 yr · Bahamut · 2014-11-24 · source ↗ · wrong label?

“The only issues I've run into are pages with large data bindings.”

mixed · production · 1.5 yr · username__ · 2014-11-24 · source ↗ · wrong label?

“I've been using Angular on-and-off in professional settings since 2012. Angular is a framework obsessed with testability that treats usability as an afterthought. That said... generally enjoy working with it.”

mixed · production · 2 yr · oinksoft · 2014-11-24 · source ↗ · wrong label?

“I've been using Angular for a SaaS for 7 months... Personally, I've not found any serious issue so far.”

endorse · production · 0.6 yr · maouida · 2014-11-24 · source ↗ · wrong label?

“I am in the middle of rewritting my own application to Angular 1.3, from an older even more obsolete framework.”

mixed · personal · smarks159 · 2014-11-01 · source ↗ · wrong label?

“I look at our application as it stands, and I regret using angular.”

regret · production · GhotiFish · 2014-10-26 · source ↗ · wrong label?

“Our end user experience was super slick using Angular, but this doesn't bode well for things that, well, aren't users (we migrated back to Rails).”

regret · production · mbesto · 2014-02-18 · source ↗ · wrong label?

“Angular/Vue/React on the front end before this.”

neutral · production · hnurl · 2025-07-18 · source ↗ · wrong label?

“"we use angular." there are no discussions or anything.”

neutral · production · bdangubic · 2024-12-27 · source ↗ · wrong label?

“We had a very large Angular 10 project that we replaced with an NX Angular project late last year.”

neutral · production · agloe_dreams · 2023-08-18 · source ↗ · wrong label?

“The client was basically letting us go while we migrated to Angular but wanted to keep maintaining Ember code.”

neutral · production · bluSCALE4 · 2023-05-20 · source ↗ · wrong label?

“(Been using preact/react since 2016, angular/jquery before that)”

neutral · personal · devmunchies · 2022-12-25 · source ↗ · wrong label?

“Create a Bazel built Angular library using only the publicly available documentation.”

neutral · personal · miiiiiike · 2022-09-13 · source ↗ · wrong label?

“We would literally never use promises because we'd become so comfortable with how we (and angular) managed the lifecycle of observables.”

neutral · production · mrcartmeneses · 2022-08-16 · source ↗ · wrong label?

“we rewrote our Rails 3 app to Angular.”

neutral · production · elt · 2022-08-02 · source ↗ · wrong label?

“We had a Python + Angular stack so among our first conversations went like”

neutral · production · skytreader · 2021-12-24 · source ↗ · wrong label?

“I've been using them at works for years.”

neutral · production · lwouis · 2021-12-15 · source ↗ · wrong label?

“We use it with Angular for our web application and with Gatsbyjs/React for our production website.”

neutral · production · Yabood · 2021-12-09 · source ↗ · wrong label?

“then Angular 1.x (2015-2020), and then React (a 1 year experiment, 2018-2019).”

neutral · production · 5 yr · pixelmonkey · 2021-08-10 · source ↗ · wrong label?

“doing something modern with React or Angular. The JWT is stored in JS.”

neutral · production · deviledeggs · 2021-07-04 · source ↗ · wrong label?

“6 years ago we migrated to angular and now we are onto React and storybook”

neutral · production · apineda · 2021-06-27 · source ↗ · wrong label?

“Fullstack Angular + Node -> Backend Node with shift to TypeScript near the end”

neutral · production · bradlys · 2021-02-13 · source ↗ · wrong label?

“fixing Angular timeouts and assigning some unqiue-id's to elements that tests don't break.”

neutral · production · nisa · 2020-12-22 · source ↗ · wrong label?

“The solution we used was to make our UI in HTML/JS/Angular and have it talk to a Lisp backend with Node.js.”

neutral · production · mimixco · 2020-12-16 · source ↗ · wrong label?

“Angular without TypeScript, Angular with TypeScript, React (and that whole ecosystem)”

neutral · personal · alasdair_ · 2020-05-16 · source ↗ · wrong label?

“As someone who has web apps in production written in backbone.js, Angular, and React”

neutral · production · adatavizguy · 2019-12-21 · source ↗ · wrong label?

“we migrated from NodeJS / Angular to Haskell / Elm and couldn't be happier.”

neutral · production · seddona · 2019-10-22 · source ↗ · wrong label?

“It will be replaced when the Angular is finished being moved to Vue”

neutral · production · merpnderp · 2019-10-03 · source ↗ · wrong label?

“Our company trialed Ember this year alongside React, Angular, and Vue for a new SPA.”

neutral · production · howdydoo · 2019-09-27 · source ↗ · wrong label?

“migrated to a static WordPress site with a handful of Angular Elements”

neutral · production · buu700 · 2019-02-17 · source ↗ · wrong label?

“VueJS and Angular for frontend (different projects)”

neutral · production · manish_gill · 2018-12-26 · source ↗ · wrong label?

“I'm moving away from Angular to Vue.js”

neutral · production · woutercx · 2018-12-24 · source ↗ · wrong label?

“Over the past year we replaced an Angular front-end with the author's recommendations”

neutral · production · ehayes · 2018-10-30 · source ↗ · wrong label?

“Say what you will about Angular, but why the hate on TypeScript? I've found using TypeScript one of the better experiences I've had in the Angular ecosystem.”

neutral · personal · shusson · 2017-12-07 · source ↗ · wrong label?

“though we default to angular”

neutral · production · ix-hispana · 2017-11-29 · source ↗ · wrong label?

“After Angular 1, Ember, and React, Vue is the first JS framework”

neutral · personal · kendallpark · 2017-11-16 · source ↗ · wrong label?

“having used in prod vanilla, jquery, react, angular and Vue”

neutral · production · sametmax · 2017-09-20 · source ↗ · wrong label?

“This year, I made my first foray into building non-trivial web applications with Angular.”

neutral · personal · hluska · 2016-12-29 · source ↗ · wrong label?

“We use mostly java, swift, and JS (Angular 2)”

neutral · production · mtam · 2016-12-13 · source ↗ · wrong label?

“coming from Angular 1.0”

neutral · personal · yathern · 2016-12-12 · source ↗ · wrong label?

“As a former Angular dev gone React”

neutral · production · joshmanders · 2016-12-11 · source ↗ · wrong label?

“Coming from Angular 1.x is a very natural progression”

neutral · personal · michaelbull · 2016-11-30 · source ↗ · wrong label?

“I'm coming from an Angular and Vue background.”

neutral · personal · mipmap04 · 2016-11-30 · source ↗ · wrong label?

“Since I had been using Angular for a while on my day job, yes, Angular was the boring choice.”

neutral · production · PerfectElement · 2016-11-30 · source ↗ · wrong label?

“we are starting out with bundeling our angular app with the api by serving the angular app as dropwizard assets”

neutral · production · alxeder · 2016-07-27 · source ↗ · wrong label?

“a prototyping framework at Catalyze that's built with Angular, the same framework we use on the production front-end.”

neutral · production · ryanSrich · 2015-07-09 · source ↗ · wrong label?

“I've tried Angular and Firebase for a few small protoypes, it's incredibly fast to create something to present.”

neutral · personal · arrmn · 2015-07-01 · source ↗ · wrong label?

“have rails load miniature angular apps on a page by page basis”

neutral · production · damoncali · 2015-06-26 · source ↗ · wrong label?

“as a backend for a web app written in Angular”

neutral · production · benwilson513 · 2015-01-26 · source ↗ · wrong label?

“We maintain legacy code that has been in production for more than 8 years and write new fully unit and integration-tested code in Groovy/Grails, Ruby/Rails, Java, and Angular.”

neutral · production · throwway222 · 2014-12-03 · source ↗ · wrong label?

“I came to Knockout from using Angular”

neutral · personal · miketalley · 2014-11-19 · source ↗ · wrong label?

“we're using rc2 in production code!”

neutral · production · Bahamut · 2013-11-08 · source ↗ · wrong label?