At worst, it was a mix of old advice, bad advice, dangerous code snippets, and people treating it like Stack Overflow.
Usually the first N posts were some really shitty solutions and someone would have to scroll way down to see a reply that calls them out and offers a good solution. But someone browsing the docs are most likely to use the first solution that seems good enough, particularly beginners.
It's good to know there are bad practices out there, and the doc team should update the doc and show how to avoid bad practice.
I will happily take docs, such as rust's docs or NaCl's docs, which don't ever mention the possible of md5summing a password, to docs where there are hundreds of comments recommending exactly that terrible practice.
There are a practically infinite number of ways to do things wrong, and very few ways to do things right. Documenting the right way by exhaustively demonstrating the wrong ways is a fool's errand.
But more to the point, I will happily take no docs at all to docs that are more wrong than right.
Expecting a "doc team" for an open-source language to keep on top of what fresh hells people are doing with forever-deprecated things seems like a very big ask.
