Final Words

There's a lot to conclude, so I will start at the highest possible level and move deeper. 

I like the iMac, I like it a lot.  Personally, it's not the right type of machine for me in that I do need a higher resolution display and more memory than the iMac can offer me.  It would, however, make a great addition to the home network if I ever wanted to put an all-in-one machine somewhere else in the house.  It's a computer that can look and work as well in a kitchen as it can in an office, and that's one thing that Apple has done very right with this platform.  It took me this long to look at it, but I think that it could quite possibly be Apple's strongest offering as it accomplishes exactly what they are trying to do - which is build lifestyle computers. 

So much has changed since I started using Macs on a regular basis just a year and a half ago.  Apple has done a tremendous job of really fleshing out their own software suite; from improving their Pro applications to molding iLife and iWork into truly indispensable applications. Apple is quickly become a very vertical provider of everything that you could want to do with one of their computers.  It is because of Apple's vertical nature as a software provider to the Mac platform that they were able to begin this Intel transition so very well. 

Just about every application that I'd use is already available as a Universal binary, the only exceptions being anything from Microsoft or Adobe/Macromedia.  While I don't view Rosetta as a real option if you plan on getting any work done with an application, it is a way to ensure a very seamless transition between platforms.  It is largely because of Apple's self-sufficiency and their small size that they could undertake such a large transition and succeed so very well at it, but regardless of the reasons, the end results are positive. 

I do stand by my comments, however, that the current Intel based Macs are more of a public beta test than something to which the masses should transition.  The problem is quite plainly the dependence on Rosetta.  If you find yourself running applications that are all Universal today, then the new iMac is a wonderful solution. However, anything that requires Rosetta to run is going to hurt.  If you absolutely have to buy a machine today and it absolutely had to be an iMac, the early adopter in me would still recommend the Intel based offering, but it would be full of painful times as you wait for application support. 

This is the second Apple article that I've written where I've felt that their base memory configurations are way off balance, especially on the Intel side of things.  If you are expected to have to use Rosetta for things like Microsoft Office, you're going to need more than 512MB of memory.  And Rosetta aside, if you're going to use iLife applications as they were intended, you're going to need more than 512MB.  Given Apple's history with memory upgrades, we'll probably see them move to 1GB standard late this year with their Powermac replacement, but until then, I can at least complain. 

As far as performance of the new Intel based Macs go, at least in Universal applications, it's quite good.  While the G5 was clearly no slouch, in many cases offering performance better than a Core Solo processor, it does lose the performance per watt battle.  It's also worth noting that a pair of G5s could never make it into an iMac of this form factor, meaning that the Core Duo's dual core performance advantages are reasonable to flaunt. 

More than anything, I am interested to see how long it takes to bring Intel's compiler technology to the OS X platform.  As Johan pointed out in his series on the G5, gcc 4.0 doesn't exactly produce the best code for AMD/Intel architectures, especially when compared to Intel's own C compilers.   At last year's Fall IDF, Intel had a session on their compilers and OS X, so I tend to believe that things will get faster for Intel based Macs over time.  Not only when Rosetta is no longer needed, but also as applications are better optimized for their architecture (e.g. Quicktime). 

I'll close, as always, on a note about the future.  We've seen that today, Intel already has the performance per watt crown with the Core Duo, and they also have the power advantage, consuming a third less power than a similarly clocked G5.  Yet, the first Intel based Macs are nothing more than the G5 versions with a different motherboard and cooling.  You tend to not over-design your chassis when you are Apple; rather, you design them to be as sleek and as minimal as possible.  With the Core Duo based iMac consistently consuming 20 - 30W less than the G5 version, you can expect that the truly exciting Intel based Macs are the ones that don't look like these.  It's those that I would personally wait for. 

The Search for Universal Binaries
Comments Locked

35 Comments

View All Comments

  • Anand Lal Shimpi - Tuesday, January 31, 2006 - link

    Turning off one core leaves the full 2MB of cache for the other core to use since it is a shared L2.

    Take care,
    Anand
  • Eug - Tuesday, January 31, 2006 - link

    quote:

    Turning off one core leaves the full 2MB of cache for the other core to use since it is a shared L2.

    Take care,
    Anand

    Cool thanks.

    P.S. I have read elsewhere that the new iMac Core Duo uses less than half of the CPU's processing power to play back H.264 Hi-Def 1920x1080 video at a full 24 fps. If true, that's great, because my iMac 2.0 chokes on that. It plays back relatively smoothly, but only at about 12-15 fps.

    That bodes well for a future single-core Yonah Mac mini.

    Then again, probably not, considering that I suspect the iMac Core Duo does so well on H.264 playback because of its Radeon X1600. I'd doubt the Mac mini would get anything close to that any time soon.
  • Anand Lal Shimpi - Tuesday, January 31, 2006 - link

    Max CPU utilization (across both CPUs) when playing a 1080p stream scaled to fit the screen is about 60%, but it usually hovers below 50%. I am not sure whether or not the X1600's H.264 decode acceleration is taken advantage of (I doubt it), I'm trying to find out now. Also remember that on the PC side, the X1600 will only accelerate up to 720p.

    Take care,
    Anand

  • Anand Lal Shimpi - Tuesday, January 31, 2006 - link

    I just confirmed with ATI, the X1600's H.264 decode acceleration is currently not supported under OS X. ATI is working with Apple on trying to get the support built in, but currently it isn't there.

    Take care,
    Anand
  • Eug - Tuesday, January 31, 2006 - link

    quote:

    I just confirmed with ATI, the X1600's H.264 decode acceleration is currently not supported under OS X. ATI is working with Apple on trying to get the support built in, but currently it isn't there.

    Thanks again for the info. That's actually good news in a way. Things are looking up for that single-core Yonah Mac mini HTPC.
  • andrep74 - Tuesday, January 31, 2006 - link

    Isn't performance/Watt a function of the CPU, not the platform?
  • Kyteland - Tuesday, January 31, 2006 - link

    That picture of Jobs doesn't say "PC vs Intel" it says "PowerPC vs Intel". Jobs is just standing in the way. He's comparing the old mac to the new mac.
  • Calin - Tuesday, January 31, 2006 - link

    You could think about it that way - but in the end, the buyer is interested on the total energy consumption/heat production (as this is what he pays for, and what he must get rid of).
    Have you heard of the Toyota D4D engine? It has a record of 2.4 liter (less than a gallon) diesel fuel used per a hundred kilometers (60 miles). However, the same engine on a Land Cruiser 4x4 all options will get you much less (four times less maybe).
    It doesn't worths talking about performance per watt at the processor level, it is better at the platform level.
  • BUBKA - Tuesday, January 31, 2006 - link

    Were these benches done with a USB 2.0 device plugged in?
  • Furen - Tuesday, January 31, 2006 - link

    I was under the impression that Intel was blaming Microsoft for that, so that would not apply to OSX, though if the driver works perfectly for every platform except Napa I'd guess its a hardware problem that MS will fix in software (which is well enough as long as it works). The power consumption difference is probably less than 10W anyway. It matters on a notebook but hardly matters with a desktop.

Log in

Don't have an account? Sign up now