HackerFriction Feedback

Products · Product

Perl

Raised as a usability problem by 132 people on Hacker News over 19 years (2008–2026), in 91 threads.

Ranked by people · period

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

  1. 1
    Code is hard to read due to special variables and terse syntaxUnreviewed

    7 people in the last 5 years · 5 threads

  2. 2
    Code is unreadable, with too many ways of doing the same thingUnreviewed

    4 people in the last 5 years · 4 threads

  3. 3
    Sigils are confusing and unintuitive for beginnersUnreviewed

    4 people in the last 5 years · 4 threads

  1. 1
    Code is hard to read due to special variables and terse syntaxUnreviewed

    15 people since the beginning · 12 threads

  2. 2
    Code is unreadable, with too many ways of doing the same thingUnreviewed

    12 people since the beginning · 12 threads

  3. 3
    Sigils are confusing and unintuitive for beginnersUnreviewed

    5 people since the beginning · 5 threads

  4. 4
    Sigils mismatch declared types, making nested element access confusingUnreviewed

    4 people since the beginning · 4 threads

  5. 5
    Syntax can't be changed after adoption, so it stays hard to useUnreviewed

    4 people since the beginning · 4 threads

  6. 6
    Nested list references and dereferencing are hard to write and debugUnreviewed

    4 people since the beginning · 4 threads

  7. 7
    Multidimensional arrays and hashes are too verbose to readUnreviewed

    3 people since the beginning · 3 threads

  8. 8
    Many CPAN modules have poor documentation and no example codeUnreviewed

    3 people since the beginning · 3 threads

Every issue, all time, most people first

  1. Code is hard to read due to special variables and terse syntaxUnreviewed

    15 people since 2008, in 10 different years · 4 this year

    2008: 1 person2009: 1 person2010: 0 people2011: 1 person2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 2 people2019: 1 person2020: 0 people2021: 3 people2022: 1 person2023: 1 person2024: 1 person2025: 4 people2026: 0 people
    20082026
    Something wrong here?
  2. Code is unreadable, with too many ways of doing the same thingUnreviewed

    12 people since 2011, in 10 different years · 1 this year

    2008: 0 people2009: 0 people2010: 0 people2011: 1 person2012: 2 people2013: 1 person2014: 0 people2015: 1 person2016: 1 person2017: 0 people2018: 0 people2019: 1 person2020: 1 person2021: 2 people2022: 0 people2023: 2 people2024: 0 people2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  3. Sigils are confusing and unintuitive for beginnersUnreviewed

    5 people since 2011, in 3 different years · 1 this year

    2008: 0 people2009: 0 people2010: 0 people2011: 1 person2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 0 people2022: 0 people2023: 1 person2024: 0 people2025: 3 people2026: 0 people
    20082026
    Something wrong here?
  4. Sigils mismatch declared types, making nested element access confusingUnreviewed

    4 people since 2008, in 4 different years · 1 this year

    2008: 1 person2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 1 person2021: 0 people2022: 2 people2023: 0 people2024: 0 people2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  5. Syntax can't be changed after adoption, so it stays hard to useUnreviewed

    4 people since 2014, in 4 different years · 1 this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 1 person2015: 1 person2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 1 person2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  6. Nested list references and dereferencing are hard to write and debugUnreviewed

    4 people since 2009, in 4 different years · none this year

    2008: 0 people2009: 1 person2010: 1 person2011: 0 people2012: 0 people2013: 1 person2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 1 person2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  7. Multidimensional arrays and hashes are too verbose to readUnreviewed

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

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 1 person2020: 0 people2021: 1 person2022: 1 person2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  8. Many CPAN modules have poor documentation and no example codeUnreviewed

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

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 0 people2015: 0 people2016: 2 people2017: 0 people2018: 0 people2019: 0 people2020: 0 people2021: 1 person2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 0 people
    20082026
    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