The Fall of Stack Overflow

Re:The Fall of Stack Overflow by spaceman_2020 on Tuesday July 25, 2023 @02:55AM (#36858878)

Google keeps returning SO answer threads that are way too old to be relevant. Like a question with a top answer from 2013.

[ Parent | on HN ]

Re:The Fall of Stack Overflow by scrollaway on Tuesday July 25, 2023 @02:57AM (#36858888)

Not all ecosystems disintegrate after a couple of years. Many times an answer from 10 years ago is still extremely relevant.

[ Parent | on HN ]

Re:The Fall of Stack Overflow by spaceman_2020 on Tuesday July 25, 2023 @03:04AM (#36858933)

Not when the answer references libraries that haven't been maintained in five years or have fallen out of favor completely (like jQuery).

[ Parent | on HN ]

Re:The Fall of Stack Overflow by scrollaway on Tuesday July 25, 2023 @03:10AM (#36858980)

I understood what you meant. But first of all, many languages have libraries relevant for several decades; second, asking questions about legacy code is often valid (and often where you need the most help); third, some people even still use jquery! (Poor guys)

[ Parent | on HN ]

Re:The Fall of Stack Overflow by spaceman_2020 on Tuesday July 25, 2023 @03:17AM (#36859032)

I understand all of that - I just question Google's algorithm that prioritizes answers from 2013 vs answers from 2021 for similar queries.

[ Parent | on HN ]

Re:The Fall of Stack Overflow by nubinetwork on Tuesday July 25, 2023 @07:36AM (#36860814)

I recently was looking into why wget --quiet --content-on-error didn't output anything with a 403. Turns out its an ancient bug they never fixed... it's not documented anywhere, except some crusty old thread on SO.

[ Parent | on HN ]