-6

I asked a question about the difference that processor architectures make to compiler performance. I asked with a lot of supporting detail to make it possible for someone who knew facts to be able to say X feature of the processor directly helps compilation and I tried to avoid simple comparative "opinion-based" wording.

Still, it was closed.

We seem to have an increasing tendency to close questions as "opinion based" when I see many of them as being more, the closer doesn't know enough about the topic to know if there will be relevant facts so assumes the question leads to just opinions. Is this just "moderation activity for ego sake?"

(Yes I looked at the profile of the person who closed it and they don't seem to be an authority in this area.)

It was a real issue I was trying to get answered and I put significant work into technical preparation to seed the answers. The question just won me a silver badge for the 2,5000 views it's had so I was just reminded of how annoyed I was by the closure.

1
  • I think there is a site trend of poorly executed hardware shopping questions being placed on hold until they can be turned into clear and objective opportunities for reopening. Why attack the messenger instead of edit the post in question or ask here for community help to make things better? Are you looking for some measure of help with using the site of just interested in publishing your thoughts and venting your dissatisfaction? I enjoy helpng with the former and welcome the latter as long as discussion remains kind and civil.
    – bmike Mod
    Mar 15 '15 at 12:09
7

That question reads like you musing about benchmarks and their applicability to your specific work requirements.

Closing a question doesn't mean it needs to stay closed; it means that, in its current form, it isn't a question that will lead to a clear and canonical answer. You'll get a bunch of "well I tried this" and "maybe this will work" type stuff which is wholly not the kind of Q&A site this happens to be.

Closing a question means it needs more work.

Even your follow-up semi-answer, semi-comment comment frames how not-a-question your question was:

I thought it might be useful to add a comment on how well the 13" has worked out. The 16GB RAM helps as does the SSD so it seems faster then my iMac most of the time when compiling or running AppCode. I have noticed a tendency to hog the more if compiling - try to avoid doing big builds and lots of web browsing simultaneously.

That's not an answer, that's a single experience and some speculation.

There might well be a reasonable question in what you posted, but as it stands I agree with the moderator who closed it: it's not a question that can be answered in any other way that would lead to a useful, guiding response. Really, the only answer that can be given for "How much difference between i5 and i7 13" Macbook Pro 2014 especially for XCode & Visual Studio compilation?" is:

It depends entirely on what, specifically, you're trying to do with those IDEs.

Full stop.

You might say the benchmarks provide as much illumination as possible on the differences and that's about it. Neither of those tools have standard benchmarking suites behind them so there isn't any empirical result you can point to to understand their behavioural differences on the two difference machines.

As for your comment about the moderator: the site is community moderated, as are all Stack Exchange sites. The question was brought to the attention of the moderators by flags from your peers. It was not a lone decision.

1
  • We love our Moderators, ...we are the moderators, ...we love our self :)
    – Ruskes
    Mar 21 '15 at 22:52

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .