What to Buy

I mentioned earlier that Apple mitigates risk in its designs much like a CPU maker. It’s always considered good practice to decouple major architecture changes from process node jumps (Intel’s famous tick-tock cadence embodies this). Apple similarly tries to alternate major changes to the industrial design from significant internal component changes. Although Ivy Bridge and Kepler are all new, the former is quite similar to Sandy Bridge while the latter is really no different than integrating any other discrete GPU. The more dramatic silicon departure comes with Haswell next year, and I suspect that’s why we got the rMBP this year.

In our performance investigations I mentioned that compared to an upgraded Sandy Bridge MacBook Pro (high clocks with SSD), you won’t see tremendous performance gains from the rMBP. A quick look around Apple’s website actually shows not even a single CPU bound performance comparison between the rMBP and last year’s MacBook Pro.

The logical thing to do, if you’re the owner of a recent (2010/2011) MacBook Pro, is to wait until next year at the minimum. Haswell should bring a significant performance increase (particularly on the processor graphics front) and you’ll get it in the same chassis as what you see today.

Most users however don’t upgrade annually. If you have an older MacBook Pro, the rMBP offers all of the benefits of last year’s Sandy Bridge upgrade but in a much better package, and with vastly improved thermal characteristics. If you fall into this group, the upgrade is a no-brainer. I won’t lie, the next two years are going to be tough. Haswell is looking very good, and if Intel can pull off 14nm on time, Broadwell will be even more impressive from a graphics standpoint. You can always make the argument to hold off on an upgrade as there’s almost always something better around the corner. In my opinion you really can’t go wrong picking any of the next three years to upgrade.

Should you decide to buy today, which model should you get?

As I mentioned before, the $2199 configuration is near-perfect in my opinion, save for the 256GB of NAND flash. Apple unfortunately won’t let you upgrade storage capacity on the base MacBook Pro with Retina Display so you’re left with two options: 1) live with the 256GB and hope someone will build an aftermarket SSD in the not too distant future, or 2) buy the $2799 model. While it’s quite likely that we’ll see third party SSDs for the rMBP, I seriously doubt you’ll find one with Samsung’s PM830 controller.

I do think 256GB is livable, it’s just that 512GB is so much more comfortable.

Apple has simplified things by not allowing multiple GPU options, and the CPU options are pretty cut and dry.

If you can live with 256GB of storage, the $2199 configuration is fine. Otherwise I’d go with the upgraded $2799 model.

The question of whether or not you should opt for the 16GB memory upgrade really depends on what you do with the system and how long you expect to use it. Without any form of socketed memory expansion, you’re stuck with the amount of memory you order on the system. Thankfully 8GB is healthy by today’s standards and likely will continue to be so for the next couple of years. If your present day workloads require 8GB of memory, then the 16GB option is a must have. If you’re looking at 16GB purely as future-proofing, chances are you’ll run into processor (or storage) limitations before you feel held back by memory. That being said, if you want to be kind to the next owner, ticking the 16GB box won’t hurt.

 

Battery Life Final Words
Comments Locked

471 Comments

View All Comments

  • RaygunV - Sunday, June 24, 2012 - link

    Apple has done nothing. Higher resolutions were already in the pipeline before apple released theirs. Apple releases first only so that the public DOES think they are innovative.

    Apple has done nothing special, just using maturing technology like all vendors will.

    http://www.tomshardware.com/news/Intel-Higher-Reso...
  • designerfx - Sunday, June 24, 2012 - link

    the same as apple: improving on plenty of things while missing the boat.

    apple: lack of improvements on hardware (not their fault, but raising resolution without a substantially more powerful GPU = things tend to suck if you try to take advantage of the resolution).

    Note all the benchmarks at the scaled down resolution on the GPU testing. You don't even want to know what these games will run at with 28xx by 18xx.

    If 1680x1050 is achieving 60fps, it's not hard to guess that 15fps might be an optimistic answer at 2800x1800.

    Meanwhile, all this "Scale the appropriate elements while letting the rest display full resolution" is an important part of the OS that windows 8 probably will miss, entirely.
  • Spunjji - Monday, June 25, 2012 - link

    Sony, Vaio Z, 13" 1920x1080. Thanks, Apple? :|
  • starburns - Monday, June 25, 2012 - link

    http://en.wikipedia.org/wiki/Ultra_High_Definition...

    Super resolutions have been around since 2005, this retina display is still only half the resolution that other companies have achieved years ago.
  • KitsuneKnight - Saturday, July 7, 2012 - link

    Displays that cost enough to buy 5+ of these laptops (if you find them on firesale!). Not really comparable.
  • optics261 - Saturday, June 23, 2012 - link

    One review to rule them all!
  • zappb - Saturday, June 23, 2012 - link

    With 4k resolution screens to bind them. Apple=progress (finally).

    After years of ignoring screen quality Lenovo, dell, hp....thanks pingguo.
  • yhselp - Saturday, June 23, 2012 - link

    One Review to rule them all, One Review to show them, One Review to teach them all and in the darkness more objective make them.
  • eron - Saturday, June 23, 2012 - link

    What software was used to measure the frame rate?
  • Spoony - Saturday, June 23, 2012 - link

    Quartz Debug. Part of Apple's developer tools. There is a string you can use to expose additional functionality in Quartz Debug such as resolution scaling factor and manual GPU switching.

    $ defaults write com.apple.QuartzDebug QuartzDebugPrivateInterface -boolean YES

Log in

Don't have an account? Sign up now