Timeline for Is this really the sort of answer we as a community want on our site?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 29, 2011 at 10:40 | comment | added | Kissaki | Even with that hypothetical question you can give good reasons WHY Microsoft won’t do it. | |
| Jun 28, 2011 at 15:54 | comment | added | user281377 | Aaronaught: when I wrote my answer and the comment above, I hadn't learned about the original question yet; that's why my answer contains a bit of speculation. | |
| Jun 28, 2011 at 15:46 | comment | added | Nicole | @ChrisF - Great point. In addition, it really irks me when a tough question is answered with the first thing that comes to mind by several people who don't really know enough to give a good answer -- rather than waiting for someone qualified to answer. Which is another reason why downvotes are so important. | |
| Jun 28, 2011 at 14:24 | comment | added | Aaronaught | What you're referring to is speculation, which is already expressly prohibited across the entire network. In this case, I don't think that the question was stupid, and some of the answers do provide insight. A lot of things sound stupidly obvious when you've only ever been exposed to one side of the issue; if you take the time to explain your perspective then that's completely OK, but if you declare it as the truth, end of conversation, then you're doing everybody (including yourself) a disservice. | |
| Jun 28, 2011 at 10:22 | comment | added | user281377 | ChrisF: I tend to agree with you, but real-life question might be less obviously stupid than my hypothetical example. | |
| Jun 28, 2011 at 9:41 | comment | added | ChrisF Mod | In that case should you really be answering the question at all? Sorry if this sounds harsh, but that case you should be voting to close as not constructive/not a real question rather than answering. | |
| Jun 28, 2011 at 9:37 | history | answered | user281377 | CC BY-SA 3.0 |