pgiguere1
macrumors 68020
Do you mean Apple's engineers are bad at programming? 😉
Not all tasks can be parallelized, which means some are single threaded and you can't do anything about it...
WebKit is an open-source engine which a lot of different companies contributed to so not only Apple is responsible for it, but it's them that I consider responsible for releasing the rMBP without making sure they can deliver appropriate software along with it.
Visibly a lot of task could have been parallelized, judging by Safari 6 vs WebKit nightly's UI performance. I'm not sure exactly what has been optimized, but the difference is massive on a rMBP. I think whatever fixes the framerate issues in Safari 7 should have been available in Safari 6, and even them I'm generous since Safari 6 launched after the rMBP.
Apple must have had so much rMBP returns because of that, not to mention worse reviews and the public's false assumption that a powerful GPU is needed to drive a high-res display, which may hurt the 13" rMBP's sales even in the long run.