Jon'sLightBulbs said:
But much more importantly, you leave software developers in the dark as well in order to keep this veil of secrecy and keep current stock moving. The result is that absolutely no native apps are availible at the Intel Imac launch. Rosetta emulation of Adobe apps is pitiful, and no Apple pro apps are emulated at all.
The secrecy really bit apple in the butt this time.
That doesn't make any sense. Apple pro apps are late because only Apple had advance warning about the transition? Apple pro apps are coming in March. And Universal Binaries ARE available, in fact they were from some companies even BEFORE the Intel Mac launch. Obviously there's a ramp-up happening rather than instant availability of all-native apps. There's no avoiding that. And Rosetta is a great transitional technology that is doing its job well--to the point where a great many users for a great many tasks will never even notice the difference. For other tasks, they will. It's a big transition and that's life. It's temporary.
Regarding Apple's secrecy being the problem here:
* Apple DID give developers a LOT of warning--LONG before last year: they told developers to get their apps onto Xcode. They made clear that Xcode--and preferably Cocoa--was the future. Apple wasn't kidding. Xcode is the key to Universal Binaries, and developers that listened to Apple's early warnings were in far better shape to get their apps Intel-native.
* If Apple had told developers about Intel even earlier--before the details and the tools were finalized--it wouldn't have necessarily helped them. Developers wouldn't have had enough to work with. They would have been given a moving target, which mean wasted money and wasted time. That's doing nobody any favors. Waiting until you have the tools ready to hand over is exactly what Apple should have done--and they did.
* The time-frame for Universal Binaries, for many apps, is nothing to do with Apple: the porting will await the next major version of the software. Why would Adobe do massive work porting CS2, even while another team works on CS3? It would be a huge waste for them. Instead, it will be CS3 that's Intel-native. And Apple giving Adobe extra notice of the Intel change wasn't going to make them finish CS3 faster. CS3 (or any other big new version of a major app) is its own project with its own schedule, and Apple can't dictate the timing.
* "Just check the little box" is absolutely true for some apps--especially ones made by developers who followed Apple guidelines (aka advance warning) in recent years. For other apps it's much harder, and for most it's in the middle. Apple never suggested otherwise.
It sounds like you may be an iMac G5 owner who is upset about things advancing so quickly--and we've all felt that frustration at some point. But that always happens with computers--there is ALWAYS something better on the way and Apple "secrecy" should never make anyone doubt that.
And Apple's secrecy about upcoming products IS very important--just like for any company, but more so when you're competing against Microsoft. You may think Apple should have stopped selling Macs during the holiday shopping season, and told everyone early about Intel's Core Duo release. I can understand why you'd want that, but it doesn't make business sense.
(PS, is this like the "iWork sales sluggish" rumor?

)