Products · Product
Angular
Raised as a usability problem by 240 people on Hacker News over 14 years (2013–2026), in 177 threads.
No issue was raised by at least 3 people in 3 threads this year.
- 1
- 2
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
Every issue, all time, most people first
Hard to learn because standard documentation is poorUnreviewed
20132026- Learning Angular's mix of multiple ways to do everything is hard2025-01-16
- Angular tooling is awful and inline docs are missing for many libraries2024-03-22
- Working on Angular projects is consistently miserable for developers2024-03-21
Directives are confusing for learners at firstUnreviewed
20132026- Hard to figure out Angular 2's new directives for simple rendering tasks2017-12-13
- Directives and scope/binding are complicated to use and understand2016-08-17
- Directives are unnecessarily hard to write2016-08-14
Error messages and stack traces don't help debuggingUnreviewed
20132026- Debugging shows giant incomprehensible call stacks because of framework magic2022-11-17
- Error messages and stack traces are useless, so debugging is hard2021-11-04
- Framework magic and zones make runtime errors and stack traces impossible to debug2021-11-04
Too many framework concepts make apps hard to buildUnreviewed
20132026- Framework has no clear philosophy, just a jumbled mess of concepts2024-06-17
- Framework is overly verbose and complex, making web app development a pain2024-03-21
- Framework feels overcomplicated, convoluted and not obvious, with a poor developer experience2020-11-19
Verbose component declarations make small components painfulUnreviewed
20132026- Hard to use composition like React's children, so components are harder to build2023-05-04
- Dynamically creating components was painful to get right2017-12-07
- Too much idiosyncratic boilerplate needed just to get started2017-06-18
Builds get slower with each version, wasting waiting timeUnreviewed
20132026- An update bumped build times to several minutes, slowing developers down2024-06-19
- Opaque CLI made recurring dev build stacktraces take two weeks to diagnose2023-05-04
- VS Code extensions are slow and often malfunction, and builds are slow2022-03-01
Steep learning curve that is hard to get pastUnreviewed
20132026- Steep learning curve that is hard to get past2022-03-01
- Steep learning curve because knowledge of JavaScript and browser APIs doesn't carry over2017-07-09
- Very steep learning curve and over-engineered for developers to learn2015-01-29
Template syntax is inconsistent and hard to work withUnreviewed
20132026- Template syntax is so complex and inconsistent that it is hard to work with2017-06-30
- Template pipe and parentheses syntax is unintuitive and poorly documented, so it's hard to learn2016-09-15
- Bracket and parenthesis binding syntax is incompatible with HTML/XML, so templates are not standards-compliant2016-01-05
Syntax and two-way databinding are awkward to useUnreviewed
20132026- Confusing mixed syntax for bidirectional binding like [(ngModel)]2016-09-15
- Angular's syntax and two-way databinding are awkward and it feels overly complex2014-10-14
- Ng-model binding meaning depends on interaction order, impossible to tell by reading2014-10-03
Scopes, transclusions and directives are hard to reason aboutUnreviewed
20132026- Google's documentation for isolated-scope directives is bad, making them hard to understand2015-09-23
- Scope declarations are scattered everywhere, so developers can't find what they're looking for2015-04-05
- Scopes, transclusions and directives are confusing to reason about2014-07-01
ng-template is confusing and exposes low-level internalsUnreviewed
20132026- Ng-template is confusing and exposes low-level internals rather than being easy to use2020-02-07
- Single ng-view makes a simple two column layout frustratingly complicated2014-03-26
- Proprietary template attributes are confusing; hard to tell where ng-repeat belongs2013-02-05
Slow web components freeze the app inside ng-repeatUnreviewed
20132026- Basic components perform far slower than native browser features they replace2025-05-16
- Official Angular CLI was painfully slow on Windows machines2016-11-15
- Slow web components bring the whole application to its knees in ng-repeat2014-11-24
Too many form approaches, unclear which fits a componentUnreviewed
20132026- Too many concepts that tie together magically, making simple form fields a nightmare2020-02-07
- Too many ways to build forms, and unclear which one works for a given component2017-06-30
- Requires many verbose attributes on the form element, making the code hard to write2013-07-22
Pages are sluggish to interact with, especially on phonesUnreviewed
20132026- Takes 5-6 seconds to load on an Android phone, versus under one second in a browser2016-09-07
- Page or app is sluggish to interact with, especially on phones2016-07-12
- Page with many widgets is slow to use on mobile2013-02-11
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 50 complaints
- HTTP requests forced into observables adds overhead and complexity, making the library confusing2026-06-03
- Showcase widgets use arrow keys instead of the expected Tab and Shift+Tab navigation2026-06-03
- Default observable return values force developers into unwanted complexity, making the API a massive pain2026-06-03
- Hard to use a custom toolchain instead of the Angular CLI2026-06-03
- Docs and answers mismatch the project's version, so code silently fails to work2026-05-26
- Commenter found AngularJS sites very confusing to work on2026-02-17
- Large Angular project was so painful to work in it caused the commenter PTSD-like burnout2025-09-16
- Editor language server crashes or freezes, leaving broken diagnostics and slow go-to-definition2025-09-15
- Templates in .html files are full of nonstandard attributes, so designers get trapped and struggle to make things work2025-07-21
- Basic components perform far slower than native browser features they replace2025-05-16
- Back button keeps sending users to the route they just left2025-04-08
- Learning Angular's mix of multiple ways to do everything is hard2025-01-16
- An update bumped build times to several minutes, slowing developers down2024-06-19
- Framework has no clear philosophy, just a jumbled mess of concepts2024-06-17
- Zone.js silently drops developers into poor performance without them realizing how2024-06-17
- Angular tooling is awful and inline docs are missing for many libraries2024-03-22
- Working on Angular projects is consistently miserable for developers2024-03-21
- Framework is overly verbose and complex, making web app development a pain2024-03-21
- Reading simple state like query params requires subscriptions that fire spuriously, making code hard to reason about2024-03-21
- Angular Router updates query params in unexpected ways, costing hours to get working2024-03-21
- Angular codebase was too complicated for the developer to understand2023-10-18
- Angular's documentation is impossible to follow2023-07-06
- Getting templates type-checked needs many non-obvious config steps and an editor plugin2023-05-04
- Migrated UI has major styling regressions users disliked, forcing a downgrade2023-05-04
- Opaque CLI made recurring dev build stacktraces take two weeks to diagnose2023-05-04
- Hard to use composition like React's children, so components are harder to build2023-05-04
- Developers struggle to grasp RxJS and manually call detectChanges everywhere2023-03-24
- Performance pitfalls easy to hit; OnPush must be manually set in every component2023-03-08
- Client-side JavaScript framework makes sites slower and less accessible for users2023-02-03
- Debugging shows giant incomprehensible call stacks because of framework magic2022-11-17
- Pipes and streams are too complicated to read a simple variable value2022-09-08
- RxJS reactive patterns get super confusing fast in larger apps2022-09-08
- Makes fetches hard to think of as streams that refresh over time2022-08-17
- Implicit dependency injection makes fixing code-splitting take a week2022-07-11
- Slow rebuilds, slow unit test startup, no hot reload, awkward router API2022-06-28
- Developer experience is frustrating; many things seem overly complicated or poorly designed2022-06-28
- Frustrating to work with, with poorly designed corners found weekly2022-06-05
- Defaults and best practices lead developers into failure rather than success2022-06-03
- Back button loses form data; autocomplete breaks input validation2022-05-04
- Steep learning curve that is hard to get past2022-03-01
- VS Code extensions are slow and often malfunction, and builds are slow2022-03-01
- Reactive forms are clunky and untyped, and templating feels like a separate language2022-02-16
- Clicking the sound button rotates the block instead, so the mute control does not work2022-02-05
- Clicking the buttons directly rotates pieces instead; must click just to their left2022-02-05
- No exit, menu, back or help buttons; controls like ASD keys fail and feel awkward2022-02-05
- Keyboard controls are non-intuitive, and the playing field makes piece position hard to judge2022-02-05
- Where pieces should go is unintuitive and requires thinking, too slow for play2022-02-05
- Controls are not intuitive to figure out2022-02-05
- RxJS is too low-level, easy to shoot yourself in the foot with2022-01-14
- Small projects require too many files, which is overwhelming to work with2022-01-13