Yocto

Raised as a usability problem by 11 people on Hacker News over 10 years (2017–2026), in 9 threads.

People raised many different problems with Yocto, 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 11 complaints

Developing for embedded Linux is so complicated that Yocto is needed to work around it2026-06-22
Builds take ridiculously long because every package is compiled from source2025-04-11
Setting up layers, commits, directory structure and config files is tedious and error-prone2025-02-21
Build errors are hard to understand, and finding package names requires guessing and waiting for failures2024-10-06
Build system so complicated that fitting layers together takes months2023-06-16
Config fragment creation process is opaque, requiring many non-obvious manual steps2023-02-28
Manual is a wall of text that doesn't explain how to do concrete tasks2019-12-02
Steep learning curve and confusing setup make it a mess for engineers2019-12-01
Fragile, undocumented, hard-to-discover configuration; errors show Python stacktraces2019-12-01
Simple list additions hit confusing syntax gotchas; steep learning curve blocks trivial tasks2019-12-01
Values are defined several layers away from the file being read, hard to trace2018-09-28