HackerFriction Feedback

Products · Product

PHP

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

Ranked by people · period

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

  1. 1
    Inconsistent function names and argument orders are hard to rememberUnreviewed

    8 people in the last 5 years · 7 threads

  2. 2
    New syntax features are confusing and hard to readUnreviewed

    3 people in the last 5 years · 3 threads

  1. 1
    Inconsistent function names and argument orders are hard to rememberUnreviewed

    47 people since the beginning · 39 threads

  2. 2
    New syntax features are confusing and hard to readUnreviewed

    8 people since the beginning · 8 threads

  3. 3
    Surprising behaviours and hidden pitfalls make the language error-proneUnreviewed

    8 people since the beginning · 8 threads

  4. 4
    Errors are silently swallowed, so developers can't tell something failedUnreviewed

    6 people since the beginning · 6 threads

  5. 5
    Configuring PHP with a webserver is cumbersome and confusingUnreviewed

    5 people since the beginning · 5 threads

  6. 6
    Numeric string keys silently converted to integers, breaking dictionariesUnreviewed

    3 people since the beginning · 3 threads

  7. 7
    The == operator behaves so unpredictably developers are told to avoid itUnreviewed

    3 people since the beginning · 3 threads

  8. 8
    array_filter behaves oddly on key-value arrays, breaking functional codeUnreviewed

    3 people since the beginning · 3 threads

Every issue, all time, most people first

  1. Inconsistent function names and argument orders are hard to rememberUnreviewed

    47 people since 2008, in 17 different years · 1 this year

    2008: 1 person2009: 2 people2010: 3 people2011: 4 people2012: 6 people2013: 1 person2014: 3 people2015: 0 people2016: 1 person2017: 4 people2018: 3 people2019: 6 people2020: 5 people2021: 0 people2022: 2 people2023: 2 people2024: 2 people2025: 1 person2026: 1 person
    20082026
    Something wrong here?
  2. New syntax features are confusing and hard to readUnreviewed

    8 people since 2010, in 8 different years · 1 this year

    2008: 0 people2009: 0 people2010: 1 person2011: 1 person2012: 1 person2013: 1 person2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 1 person2021: 1 person2022: 0 people2023: 0 people2024: 1 person2025: 1 person2026: 0 people
    20082026
    Something wrong here?
  3. Surprising behaviours and hidden pitfalls make the language error-proneUnreviewed

    8 people since 2012, in 7 different years · none this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 2 people2013: 0 people2014: 1 person2015: 1 person2016: 1 person2017: 0 people2018: 0 people2019: 0 people2020: 1 person2021: 0 people2022: 1 person2023: 1 person2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  4. Errors are silently swallowed, so developers can't tell something failedUnreviewed

    6 people since 2010, in 5 different years · none this year

    2008: 0 people2009: 0 people2010: 1 person2011: 0 people2012: 1 person2013: 0 people2014: 1 person2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 0 people2020: 2 people2021: 0 people2022: 0 people2023: 1 person2024: 0 people2025: 0 people2026: 0 people
    20082026
    Something wrong here?
  5. Configuring PHP with a webserver is cumbersome and confusingUnreviewed

    5 people since 2012, in 5 different years · 1 this year

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 1 person2013: 0 people2014: 0 people2015: 0 people2016: 0 people2017: 0 people2018: 1 person2019: 0 people2020: 1 person2021: 0 people2022: 0 people2023: 1 person2024: 0 people2025: 0 people2026: 1 person
    20082026
    Something wrong here?
  6. Numeric string keys silently converted to integers, breaking dictionariesUnreviewed

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

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 1 person2013: 0 people2014: 0 people2015: 1 person2016: 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. The == operator behaves so unpredictably developers are told to avoid itUnreviewed

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

    2008: 0 people2009: 0 people2010: 0 people2011: 0 people2012: 0 people2013: 0 people2014: 1 person2015: 0 people2016: 0 people2017: 0 people2018: 0 people2019: 1 person2020: 0 people2021: 0 people2022: 0 people2023: 0 people2024: 0 people2025: 0 people2026: 1 person
    20082026
    Something wrong here?
  8. array_filter behaves oddly on key-value arrays, breaking functional codeUnreviewed

    3 people since 2021, in 2 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: 0 people2020: 0 people2021: 1 person2022: 0 people2023: 0 people2024: 0 people2025: 2 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