The recent discussion around the WebServer Benchmarks question has me thinking.
This question poses a generally useful query that doesn't have one true answer. Part of our mission is to understand the usefulness of "Good Subjective" questions to the rest of the community.
Our current "opinion-based" close reason is not up to the task of indicating that "Good Subjective" questions still have a home at ServerFault and the other StackExchange sites.
The current wording is:
primarily opinion-based Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.
This close reason should be re-worded to better convey this core principle and encourage new question reviewers not to close subjective questions that have merit and value for Professional system and network administrators.
I'd like to reboot this discussion, especially in light of our recent discussions on recruiting and retaining more talent.
Whether we admit it or not, a fair amount of professional system administration is subjective. Every org and/or admin has their own rules of thumb where there is no best practice or where best practice simply cannot apply. In lieu of A question about padding host names, but there are other examples as well, even ones that we cannot foresee. Yes, some answers can be opinion based, but answers can also be based on logic as well, and all answers are subject to voting.
So, should "Good" subjective questions be subject to closure? Should we take time to define "Good"? In my example above the OP took time to do some research first on his own. It is also a question relevant to professional system administration. The question can generate many answers, but they will not all be of the same caliber. Saying "We don't do that here, what's the big deal" is a terrible answer, and not based on
facts, references, or specific expertise. My answer, however, is still opinion based, but there's logic behind it, as well as Pros and Cons weighed within.
Looking just now to copy the hyperlink, I see that question was closed. Pity. Guess what the closed reason is?
Benchmarks not specific to your environment are worthless 80-90% of the time.