Affiliate Disclosure
If you buy through our links, we may get a commission. Read our ethics policy.

Intel Macs a focus of Apple's forthcoming Tiger update

A forthcoming 10.4.10 release of Apple's Mac OS X Tiger operating system will offer the greatest benefit to users of its Intel-based Macs, according to reports.

The Mac maker, which began evaluating the Tiger maintenance update in May, has since issued a number a test builds to its vast developer the community. The latest such seeds were reported to have arrived during the firm's annual developers conference this week, carrying build numbers 8R214 and 8R2214 for PowerPC- and Intel-based Macs, respectively.

For the most part, Apple is working to increase the stability and performance of Tiger ahead of October's Leopard release, using recent builds of the impending update to address issues within the software's kernel, JavaScript core and OpenGL engines.

People familiar with the latest tests seeds say improvements to imaging, specifically fixes for RAW format support, have also emerged as a primary focus.

Of two distributions — PowerPC and Intel — Apple has asked its developers to test the latter more broadly, those people say. Areas of focus for the Intel version not emphasized with the PowerPC software reportedly include audio, video, graphics and Bluetooth technology.

It's unclear when Apple plans to release Mac OS X 10.4.10 or whether the company's upcoming iPhone device will have any dependencies on refinements included in the OS update.

The current version of Tiger is Mac OS X 10.4.9, which was released in March.



21 Comments

jpferreira 18 Years · 19 comments

wtf?? ppc is not dead... i've got an 'old' g4700 imac and it's still running photoshop pretty fine.. of course, it's not a g5 or anything but it's a four y/o machine! i think these intel machines won't last this much....

why not focus on ppc either, apple? as far as we can guess, leopard is gonna be much more hardware consuming than tiger and probably there's a lot of ppc out there that won't make the transition...

bad....

Marvin 18 Years · 15355 comments

Quote:
Originally Posted by AppleInsider

For the most part, Apple is working to increase the stability and performance of Tiger ahead of October's Leopard release, using recent builds of the impending update to address issues within the software's kernel, JavaScript core and OpenGL engines.

Let's hope these issues are fixed once and for all.

zozo 18 Years · 1 comment

Quote:
Originally Posted by jpferreira

wtf?? ppc is not dead... i've got an 'old' g4700 imac and it's still running photoshop pretty fine.. of course, it's not a g5 or anything but it's a four y/o machine! i think these intel machines won't last this much....

why not focus on ppc either, apple? as far as we can guess, leopard is gonna be much more hardware consuming than tiger and probably there's a lot of ppc out there that won't make the transition...

bad....

Maybe there are just more troubles with Tiger on Intel. They had more time to work on the PPC version before.

louzer 20 Years · 1054 comments

Quote:
Originally Posted by jpferreira

wtf?? ppc is not dead... i've got an 'old' g4700 imac and it's still running photoshop pretty fine.. of course, it's not a g5 or anything but it's a four y/o machine! i think these intel machines won't last this much....

why not focus on ppc either, apple? as far as we can guess, leopard is gonna be much more hardware consuming than tiger and probably there's a lot of ppc out there that won't make the transition...

bad....

Why not? There's no money in it. If they focus on Intel, it could actually help push a hardware sale. But offering updates for you lousy penny-pinching free-loaders, expecting to use your computer for years, with Apple getting nothing out of it. Come on, buy an intel mac. You know they want you to....

But zozo is right. The PPC version is way older then the intel version, and, as such, as more debugging time in it already (I don't care what Apple says, there's still differences between the platforms that require separate coding and debugging)