Products · Broad category
Development environments
Raised as a usability problem by 12 people on Hacker News over 15 years (2011–2025), in 12 threads.
This is a broad category rather than one product, so its issues aren't ranked on the home page.
People raised many different problems with Development environments, 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 12 complaints
- Each language's dependency manager needs extra setup steps, so projects are hard to get running quickly2025-01-14
- Projects cluttered with many config files in different formats, nested and escaped inside each other2023-08-23
- Setting up old projects requires checking many files, outdated docs, guessing and asking people2023-03-06
- Full of sharp edges, needed arcane knowledge and incantations to use2022-02-21
- Renewal terms hidden at bottom of page, hard to notice before charge2021-02-08
- Tooling relies on environment variables, so built products are hard to use on other machines and scripts can't wrap it2021-02-08
- Tools break or need updating after months away, wasting hours before any coding can start2020-06-08
- Programming inside the container feels slow and laggy to work in2020-05-22
- Setting up a language environment means hours of searching cryptic package error codes2017-08-14
- Poorly documented multi-step setup needs repeated help from one person to work2016-08-15
- Every development stack causes repeated frustration and needing many searches to get working2012-04-10
- Beginners can't tell which compiler to download, how to install it, or where to get help2011-11-07