News for hackers. Stuff that matters.
Re:Deoptimizing a C++ program by billforsternz on Sunday May 22, 2016 @04:49PM (#11750230)
Inevitably the stackoverflow mods have moved into shut this down. They should be honest and introduce a "too interesting" classification, complete with a wordy, humorless justification phrase.
Re:Deoptimizing a C++ program by mixedmath on Sunday May 22, 2016 @06:12PM (#11750507)
I should note that this wasn't closed by moderators, but instead just normal StackOverflow users. In fact, one of the mods commented on the question before it was closed (and did not close the question).
Re:Deoptimizing a C++ program by billforsternz on Sunday May 22, 2016 @07:35PM (#11750769)
Good point (upvoted), I would edit my comment but it is too late for that. My comment was a little snarky, but my greater point is that I don't like the excessive moderation culture that has developed there. Sure clear out the junk and spam, trim the paths and clear the weeds. But don't insist on a literal interpretation of excessively pedantic guidelines when the content is clearly of high quality and is being strongly upvoted as a reflection of that.
Re:Deoptimizing a C++ program by kristianp on Sunday May 22, 2016 @08:40PM (#11751024)
I don't follow what you mean, normal users are moderators, just they're just users with sufficient karma.
Re:Deoptimizing a C++ program by caf on Sunday May 22, 2016 @09:17PM (#11751147)
Stackoverflow does have a separate concept of "Moderator", which is a voted-on position and denoted by a blue diamond next to their name.
Re:Deoptimizing a C++ program by Zergy on Sunday May 22, 2016 @06:03PM (#11750478)
SO has very specific goals and being interesting or a forum for discussion is not one of them. While I do think they are occasionally to strict I don't think is is one such case, I would have voted to close.
Re:Deoptimizing a C++ program by jsmeaton on Monday May 23, 2016 @06:23AM (#11752908)
I'm sort of OK with most discussion based questions and answers being shut down. This particular question is well asked, is focused (i7 pipeline de-optimizations), and has a few answers that have very specific information related to the question. There is no discussion happening in the answers. There's no way this question should be closed, and I've voted to reopen.
Re:Deoptimizing a C++ program by eru on Sunday May 22, 2016 @08:22PM (#11750962)
Perhaps instead of closing, they should just `promote' content to a discussion site.
Re:Deoptimizing a C++ program by Zergy on Sunday May 29, 2016 @08:30PM (#11798938)
If there is an appropriate SE site moderators can already do this.If not users can do this by copying and pasting the question into the submission box for a more appropriate site.
Re:Deoptimizing a C++ program by maaaats on Sunday May 22, 2016 @06:17PM (#11750520)
It was closed by regular users. If you would like to see it open, vote to reopen it.

However, the question is broad and vague, and doesn't really fit the SO model.

Re:Deoptimizing a C++ program by pcordes on Sunday May 22, 2016 @06:37PM (#11750589)
I'd love it if the OP would clarify what kinds of things are and aren't allowed. I voted to reopen even without that, since I thought it was an interesting question.

Every rule has exceptions, and judging from the voting clearly a lot of people are ok with allowing this specific exception to the rules.

I just wish the 100 votes were spread out over more days. I answered because I personally thought it was interesting, and I'm not really a rep whore, but still. :P

Re:Deoptimizing a C++ program by ghayes on Sunday May 22, 2016 @07:18PM (#11750715)
It looks open right now to me (with one vote to close).