[wpietri]

Have you considered that the problem here is not insufficient explanation of policy?

There's this thing that some programmers do a lot, where it's the users who are wrong. Using it wrong, approaching it wrong, thinking about it wrong, wanting the wrong thing. Just not understanding enough the masterwork that the programmers created.

What this view misses is that the users are the point. If one user gets it wrong, sure, maybe it's the user. But broadly the point of software is to serve and adapt to users, and developers who forget that are starting an argument that they cannot win in the long term.

It's especially wild to see you talking like this on an article about how Stack Overflow is just about dead. It needed changes a decade ago, but everyone just hunkered down and defended the existing approach. The policies you are somehow still defending are a big part of what doomed the site.

[shagie]

The site was a consensus of what Jeff and Joel and their associated blogging communities who started posting on Stack Overflow wanted. There was some tension between those two communities about what should be there, but that's where it started.

In the early days, onboarding was done fairly actively with a reasonable amount of the community participating in answering and community moderation - shaping it.

That portion of the community - both answering and moderating was key for onboarding.

However, as Stack Overflow got popular, a smaller and smaller percent of the community was actively answering and participating in community moderation - and onboarding of new people became more and more difficult.

Here I lay the responsibility nearly completely at the feet of corporate. The friction for moderation was increased at the same time that it became popular and thus harder for the community to moderate.

Making it easier moderate and help people understand the site meant that either you needed a larger part of the now very large number of people participating on the site or the ease of community moderation needed to be dialed back.

This is also where rudeness became more and more common. There are two parts to this - first rudeness takes no points to get to that level of moderation. It doesn't have any limited pool of votes that you deplete. Secondly, not everything was rude. With the smaller and smaller pool of community moderation people were shorter in their attempts to onboard a person. You couldn't write a paragraph in a comment and spend 10 minutes on one person when spending 1 minute on 10 different people was more likely to help someone. The shortness of responses was interpreted by the person asking was being perceived as rude.

Lastly, StackOverflow was designed as a Q&A site and attempted to minimize some of the things that were seen as failings described in A Group Is Its Own Worst Enemy ( https://news.ycombinator.com/item?id=23723205 ) - Clay Shirky was a mentor of Jeff and was on the original Stack Overflow board. It tried (and for a long time succeeded at) handling scale... though when Stack Overflow's ability to handle scale failed, it was the moderation tools and the ability for the people participating in community moderation to help surface the good questions to be answered and have the questions that needed work to be properly answerable in the Q&A format that Stack Overflow was designed around (not in a forum format) that suffered.

[zahlman]

What you're missing is that random people who come to Stack Overflow to ask a question (of a sort that doesn't meet the site's standards) are not my "users". I don't care in the slightest about these metrics of "dead-ness", and showing them to me another hundred times will not change my mind about that.

Because from my perspective, it has never been about how many questions are asked per day, or how many ad impressions the site owners get. (I don't see a dime from it, after all.) From my perspective, way too many questions got asked. It is more than three times as many publicly visible and still-open questions, as there are articles on Wikipedia. For a scope of "practical matters about writing code", as compared to "any real-world phenomenon important enough for reliable sources to have written about it".

I am not trying to win the argument about what people want. I am only establishing that the goal is legitimate, and that people who share that goal should be permitted to congregate in public and try to accomplish something. I do not share your goals. The community is not like software, and "serving and adapting to users" does not benefit the people doing the work. We never arranged to have the kind of "users" you describe.

[immibis]

Deadness is the symptom, not the cause. Users don't avoid SO because it's dead, but rather, SO is dead because users avoid it. It's up to you to figure out why users are avoiding it. Hint: They've been telling you quite loudly.

There's another thread on the front page about IPv6 where someone had a good analogy: IPv4 vs IPv6 is like Python 2 vs 3. The Python 2 diehards continued arguing furiously to an emptier and emptier room. They never felt they were proven wrong, and the intensity of the argument never diminished but the argument was with fewer and fewer people until they were just arguing with themselves as the world moved on without them.

And that's exactly what happened to Stack Overflow, and you're one of those guys still trying to promote the use of Python 2.7 in 2026, after the horse is long gone. Everyone has left, the lights are off in the empty debate hall and you're standing there at the podium telling a bunch of chairs and desks why everyone actually agrees with you. You might want to reflect on why you hold such fervent beliefs that are in direct contradiction with observable reality. Can I guess you had a lot of reputation points and you desperately don't want to believe they're worthless now?

The referenced comment: https://news.ycombinator.com/item?id=46477920

[wpietri]

As a former Wikipedia administrator, I think one of the things that Wikipedia has done exactly right is to strongly prioritize readers first, editors second, and administrators third. The unofficial Wikipedia administrator symbol is a mop, because it's much more a position of responsibility than it is a position of power.

I obviously think you and other user-hostile people should be permitted to congregate and accomplish something. What I object to in Stack Overflow's case is the site being taken over by people like that, serving themselves and their own preferences with such vigor that they alienated vast numbers of potential contributors, putting the site on a path of decline from which is unlikely to recover.

Even by your own terms, having a place for some (conveniently unspecified) group to "congregate in public and try to accomplish something" looks certain to be a failure. However much you don't care about deadness or declining revenue, the people paying the bills surely do. Stack Overflow was only a success because it served and adapted to users.

But I give you points for being honest about your hostility to the entire point of the site. It not only makes it clear why it's failing, but it'll keep people from being sorry when it gets closed down.