XAML

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

People raised many different problems with XAML, 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

Simple layouts need hundreds of lines of code and resize janky2024-04-23
Too much implicit magic makes unexpected behaviour very hard to trace2023-12-19
Some UI tasks are very hard, requiring many ValueConverters2023-09-25
Data-binding relies on mutable viewmodels and side-effects, hard to reason about2022-03-05
Documentation and resources are all XAML, making the API hard to use in pure C#2021-08-20
Databound visual tree code is opaque and impossible for developers to debug2020-01-14
Verbose mini-language for conditionals is awkward; XML lacks control structures2019-10-31
Binding values written as strings in XML attributes make typos easy to make and hard to catch2019-10-31
Intellisense gives no help with errors, forcing copy-paste trial and error in XAML2017-06-06
Steep learning curve for building anything beyond simple templates2013-01-20
Bad XAML breaks whole file with no useful error; designer shows blank files2012-06-07
Auto-generated code is mixed with hand-edited code, making it a pain to work with2011-10-26