Timeline for Why are "why was ... implemented this way" questions closed as opinion based?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 19, 2021 at 21:54 | comment | added | Vikki | "You won't get help out of it" - We'd know why such-and-such was implemented in so-and-so way, when we didn't know before. Adding to people's knowledge is inherently helpful. | |
| Apr 3, 2015 at 14:14 | comment | added | Croad Langshan | Understanding the design of tools often helps use them. I think it's a mistake to require every question to flag up their use. Instead, we should proceed as if they were asked in the spirit of good SE questions. If they were, all is good. If not, the questioner might not get what they wanted, but others likely will, because the answers will still be good answers to the generous interpretation of the question. It's only when there are multiple good (i.e. generous) interpretations that there is a problem. | |
| Apr 3, 2015 at 13:54 | comment | added | Croad Langshan | I think as answerers / moderators we should at least consider the possibility that the questioner has reasons for asking the question that can't reasonably be communicated in the SE format. Not every question we don't understand is caused by a failing of the questioner's understanding. I can for example recall times when I knew the answer to a question asked by somebody smarter than me who was pursuing a problem that I do not understand. Sometimes I even thought the question was misguided, when in fact it was not. These issues cannot always be resolved, so we shouldn't try too hard. | |
| Jan 13, 2015 at 20:03 | comment | added | Tamara Wijsman | @m4573r: (Quoting this question's title) Knowing "why ... is implemented this way" can help make a decision if you were to reimplement it. People don't see the need to mention an attempt at reimplementation, because they consider it irrelevant to the question. It only becomes relevant the moment that answers don't help; sometimes these extra missing details help, sometimes they don't. It is easy to attach whole PC specs and logs and what not; but in the end, it is a ton of noise and could even bring people on the wrong track... | |
| Jan 13, 2015 at 19:48 | comment | added | m4573r | @TomWijsman if it's not obvious, then the question might not be voted to be closed :) In your example, if the OP would like to know this information to make a decision, they would probably state it in the question, and even if not, provided the question is worded correctly, I could see a potential of helping others. I see none of that in why-doesnt-windows-command-prompt-still-support-ctrl-v | |
| Jan 13, 2015 at 19:41 | comment | added | m4573r | @MatthijsWessels The thing is, if you wanted to rebuild powershell, I'd assume the question would be a lot different (more detailed, more technical, more focused, or on the other side more theoretical, more general) if existing at all... The question as is it now won't help much rebuilding anything, and the comments about .Net breaking stuff, or the OP's opinion about "every time I press ^v I think it's high time someone changed this", leave little doubt about the intent. | |
| Jan 13, 2015 at 17:03 | comment | added | Tamara Wijsman | Sometimes it is not obvious; another example question Why did organization X create framework Y? might seem curious and subjective at first, but might be a vital part of the OPs ability to understand the difference between the frameworks and decide between them. (The better type of shopping questions) | |
| Jan 13, 2015 at 16:35 | comment | added | Matthijs Wessels | So would adding "I'm planning to rebuild powershell" above it, make it appropriate? | |
| Jan 13, 2015 at 15:56 | history | answered | m4573r | CC BY-SA 3.0 |