I noticed lately a lot of "which Mac is the best for..." questions.

Here is a list, and I practically only used the tag:

Some of them are closed, a lot still open.

So we should either close them all - in the end, they kind of belong to the shopping-style question - or, like Diago suggested for the iCloud questions, have a canonical question, with each MacBook and their specs as a separate answer, so we can close the other questions as a duplicate of this one.

My opinion would be to simply close them, but let's see what the community has to say about this.

3 Answers 3


I do like the idea of a canonical question for this one. That way, most can be closed as duplicates, and those whose authors think the canonical question doesn't answer their question can provide more information to distinguish what makes their case different. Then, if their case is different but not too localized, they can be reopened.


I would say no - don't close them unless they clearly are bad questions.

I was personally dissapointed that the "http://apple.stackexchange.com/questions/29377/which-macbook-pro-configuration-is-best-suitable-for-iphone-ipad-app-development" question got closed and will try to fix it and get it undeleted.

Even when the question is worded poorly (many of these are) and narrowly (the OP obviously is in the process of asking), I think there is a kernel of very important knowledge that is purely objective and should be questioned here to let people provide good technical answers.

Specifically, to develop iOS you have three major tasks:

  • initial design and layout of the app
  • coding and unit tests
  • running the iOS simulator
  • debugging and support

Portable macs have specific constraints that make the "design / layout" and "simulator" aspects of development problematic. Specifically, the iOS simulator wants to use 368 by 716 pixels for non retina devices, 690 by 994 pixels for retina devices and 765 by 994 for iPad simulation.

This really limits the effective use of say an 11 inch air unless you will have a monitor when you need to do the "design/layout" or want to edit code and read bug reports on the same screen as the simulator is running if you won't debug your code on an actual device and use the Mac's screen to do the dev half of the work.

So - the existing tools (flag, close, edit) work well to close questions that are vague, similar or exact duplicate or don't talk about objective Q/A.

Any hardware recommendation question is prone to uncertainty / fragmentation based on the asker and answer's personal interpretation of:

  1. cost ($4k for professional tools is a pittance if you forego $400k for an education. On the other hand, $4k for something that won't make you money for 6-16 months is a lot to spend on anything)
  2. time (students/learners vs professionals)
  3. expertise
  4. timing (do you try to time your purchase or just buy knowing macs hold their resale and you can always get most of your money back if you want a new mac in 3 months time)

When these issues are mixed with a technical discussion, the quality of the question seems to devolve rapidly and I don't think a ban will be any more effective than current mod tools.


  • 2
    Regarding the closed question, it definitely looks like a duplicate to me, is there some reason that's not the case? Commented Oct 28, 2011 at 23:00

I favor having a canonical question for them, but until one is created I think that the questions can remain open, provided they aren't duplicates.

You must log in to answer this question.

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