Products · Pattern or everyday thing
Configuration files
Raised as a usability problem by 9 people on Hacker News over 10 years (2017–2026), in 9 threads.
No issue was raised by at least 3 people in 3 threads this year.
No issue was raised by at least 3 people in 3 threads in the last 5 years.
Every issue, all time, most people first
Config files are hard to edit and behave unpredictablyUnreviewed
20172026- Human-writable config formats need external plugins or formatters to be usable2025-09-19
- Config formats are hard to edit and behave unpredictably2021-04-03
- Config formats split related data apart, so inconsistencies and typos are hard to spot visually2020-09-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 9 complaints
- Config docs say "regex" without naming the dialect, so users must guess the syntax2026-06-28
- Users must hand-edit config files, and asking them to use SQL is sadistic2025-11-17
- Human-writable config formats need external plugins or formatters to be usable2025-09-19
- Overriding defaults forces users to edit shipped files, effectively maintaining a fork, and upgrades prompt for pointless config conflicts2024-04-09
- Fully commented config files with every option make it hard to build a minimal file2021-08-22
- Config formats are hard to edit and behave unpredictably2021-04-03
- Config formats split related data apart, so inconsistencies and typos are hard to spot visually2020-09-11
- Settings' meaning, valid values and units are unclear without comments or documentation2019-04-13
- Undocumented or implicit option combinations make valid configurations hard to work out2017-09-06