HackerFriction Feedback

Products · Product

Spring Framework

Raised as a usability problem by 55 people on Hacker News over 14 years (2013–2026), in 59 threads.

Ranked by people · period

No issue was raised by at least 3 people in 3 threads this year.

  1. 1
    Annotation-driven setup is hard to debugUnreviewed

    4 people in the last 5 years · 3 threads

  2. 2
    Forces annotations and interfaces that are hard to work aroundUnreviewed

    3 people in the last 5 years · 3 threads

  3. 3
    Hard to find where a configuration property was setUnreviewed

    3 people in the last 5 years · 3 threads

  1. 1
    Finding why a bean is missing during auto configuration is hardUnreviewed

    8 people since the beginning · 8 threads

  2. 2
    Annotation-driven setup is hard to debugUnreviewed

    8 people since the beginning · 7 threads

  3. 3
    Control flow jumps between config and code, hiding misconfiguration errorsUnreviewed

    3 people since the beginning · 3 threads

  4. 4
    Forces annotations and interfaces that are hard to work aroundUnreviewed

    3 people since the beginning · 3 threads

  5. 5
    Hard to find where a configuration property was setUnreviewed

    3 people since the beginning · 3 threads

Every issue, all time, most people first

  1. Finding why a bean is missing during auto configuration is hardUnreviewed

    8 people since 2017, in 6 different years · none this year

    2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 1 person2018: 1 person2019: 2 people2020: 1 person2021: 1 person2022: 0 people2023: 2 people2024: 0 people2025: 0 people2026: 0 people
    20132026
    Something wrong here?
  2. Annotation-driven setup is hard to debugUnreviewed

    8 people since 2018, in 6 different years · 1 this year

    2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 1 person2019: 0 people2020: 2 people2021: 1 person2022: 1 person2023: 3 people2024: 0 people2025: 0 people2026: 1 person
    20132026
    Something wrong here?
  3. Control flow jumps between config and code, hiding misconfiguration errorsUnreviewed

    3 people since 2013, in 3 different years · none this year

    2013: 1 person2014: 0 people2015: 0 people2016: 1 person2017: 0 people2018: 0 people2019: 0 people2020: 1 person2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20132026
    Something wrong here?
  4. Forces annotations and interfaces that are hard to work aroundUnreviewed

    3 people since 2023, in 2 different years · none this year

    2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 2 people2024: 0 people2025: 1 person2026: 0 people
    20132026
    Something wrong here?
  5. Hard to find where a configuration property was setUnreviewed

    3 people since 2022, in 2 different years · none this year

    2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 2 people2023: 1 person2024: 0 people2025: 0 people2026: 0 people
    20132026
    Something wrong here?

This list counts all time; the period switch above only changes the ranking. Each issue is a group of similar complaints raised by at least 3 people in 3 different months and threads. Each line under an issue is Claude Haiku's summary of one of its latest comments, not a quote; follow it to read the comment on Hacker News.

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