GCC

Raised as a usability problem by 14 people on Hacker News over 16 years (2011–2026), in 13 threads.

People raised many different problems with GCC, but no single problem has yet been raised by 3 people in 3 different months and threads.

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 14 complaints

Template errors span multiple screens and omit the actual error location2026-05-21
Sheer volume of template errors buries the root cause in log spam2026-05-21
Compiler hardening interfaces poorly documented, unclear how to use them without glibc2024-06-27
Hard to set up and output not readable in source context2024-04-07
Blank page demands JavaScript; article is hidden behind an overlay that blocks reading2022-09-18
Real error line buried in long wall of macro expansions and useless suggestions2020-03-03
Without error numbers, translated errors can't be referenced except by full message text2019-02-26
Inline assembler is hard to use correctly; requires understanding register allocation2016-04-23
The C++ parse tree is hard to work with because the code is very old2014-10-06
Template errors expand to huge untypedef'd types, making compile errors pages long2014-08-04
Configure fails with unclear errors, and the cause is hidden until noticed2014-03-10
Hard to figure out which of the many options are needed2014-01-25
Sidebar takes over the phone screen, making the site unusable2013-12-03
Can't tell from compiler output which option disables a warning; needs docs searching and trial and error2011-03-27