3 ms·
Oh I love the way you put this. I just checked and I've been a member for 10 years and 6 months. I used to answer questions. A lot. In the early days (at one p
by cletus 8y ago
Oh I love the way you put this.
I just checked and I've been a member for 10 years and 6 months. I used to answer questions. A lot. In the early days (at one point it was Jon Skeet, Marc Gravelli then me) and I'm kind of surprised how much karma I still get form those old answers.
But I haven't really answered anything in 8+ years. Even one year in I commented on and started several threads on Meta about the "mod problem". And it's only gotten worse.
To riff on a phrase, "those who can, answer, those who can't, mod", which is fine, but there is a particular kind of toxic personality that gets attracted to the authority of being a mod that then appoints itself the arbiter of content. You are fighting a constant battle to keep these toxic (but well-intentioned--mostly) souls out. I saw even then the trend of closing interesting questions as "subjective".
My opinion then--and now--is you can ask a question like "what are the advantages of React.js vs Vue.js?" in an intelligent way without it being a flame war. The fact that it doesn't have an objective answer is (IMHO) irrelevant. You can divine useful information from the answers to that question that will help you go one way or the other.
There is a lot of subjectivity in programming and a lot of not strictly better solutions. Giving people some points to consider as a starting point is incredibly valuable.
- geoka9 8y agoI noticed the "subjective" closing many times and always wondered why that criterion was even introduced on SO. I mean what's wrong with a comment/question being subjective as long as it contains useful information?
- saywhatnow 8y agoI believe the thinking is that what's wrong with it is that over time it tends to attract flamewars and downvotes which are not useful to people searching for answers to their questions.