Quote:
Would it make any difference if I used 13 inch for coding in SDK for iphone apps?
NO, writing code for the iPhone is not that CPU intensive. I've seen people compile most of the "games" for iOS using a 2.0 GHz MacBook Pro.
Ultimately, it is disappointing that Apple dropped NVidia
Quote:
Typical response from the uneducated. Clock speed is no longer a clear indicator of performance and is only a small part of the package itself. The multi cores work together at the base 2.0Ghz speed but if you are running a non multi-threaded application it will 'power off' 3 cores and boost the clock speed of a single core, in this case probably to 2.8GHZ or 3.0Ghz
Normally you would be correct, however, only about 1% of applications are multi-threaded. Most are still single threaded, where a slower CPU would not perform as well as a faster one.
Also, disk I/O is still the slowest part of a computer, so having an HDD instead of a SSD also hurts performance.
So, Apple is actually jerking us around; unless you only buy/use multi-threaded applications; in which case, I guess you're fine.
As far as AMD vs NVidia: I have a pretty tight gaming rig (Windows of course) and it sucked until I got rid of the AMD 5770 and went with an NVidia GTX 470. So, I see these new MacBooks as woefully underpowered.
Is it faster than my new MacBook Air? That has yet to be seen, as I don't feel like buying a new MacBook Pro just to see how it compares video wise.
Quote:
Thunderbolt, facetimehd and sandybridge doesnt warrant me to upgrade yet.
sandybridge = stay away.
NewEgg pulled all the SandyBridge Mobo's ever since Intel announced that they have issues with their CPU (
http://pcper.com/comments.php?nid=9695)
Nice how Apple didn't seem to get that memo