I guess they have no interest/plans of selling the software to the millions of current PPC Mac owners.
Why should they when there's already plenty of similar software already available? This looks like a totally useless app.
I guess they have no interest/plans of selling the software to the millions of current PPC Mac owners.
I said it before and I'll say it again. Adobe will eventually drop all OS X development and go totally Windows. Apple will have no choice but to either go it alone with productivity applications or switch over to Windows and become a Wintel OEM.... Apple will have to do it or die.
bzgnyc said:I agree with their decision except for the problem that their big apps (e.g. CS2) are PPC-only and I think high-end users are waiting for CS3 before getting a Mac Pro. For high-end users, CS2 running on Mac Pro via Rosetta is not good enough.
Spot on. My glass is definitely half full."For intel macs only" is far better than "For Windows only". Right?
remembered Adobe Premiere Pro?
Adobe can announce tomorrow that they dropping all OS X support and that 50-70% of the market will have no choice but to either move to Windows (Intel Macs or Intel PCs) or go without.
Which Xcode box do you check to create .NET (or even Win32) applications?I wouldn't even know how to begin to write an application that couldn't be compiled for PPC by checking off the box in Xcode - except by maybe writing native Intel assembly code.
I think that it's more likely that the tsunami of "Intel-only" products is on its way.......and I think the prognosis for the G5 and G4 is very good for the next few years.
I know this kinda stuff was going to happen but not so quick. I know that intel is the future for macs but adobe making an intel only app right now seems ridiculous to me.
It depends, If you relly on Adobe CS and After Effects I would wait until the next revision of the Mac Pro. The current Mac Pro is not as fast as the PM Quad G5 for CS2 and AE. Close, but not as fast.
Next revision of the Mac Pro will be probably a little faster under Rosetta. Then, I think is the right time to move since is said by Adobe that Intel native CS will be here next spring. then the Mac Pro will kick a**!
Depends on who you are, mate. As long as Apple keeps supporting PPC with FinalCut Suite (or derivative), I will keep using my Powermacs. I would love to see some panic and fire sale on G5 Quads.
Which Xcode box do you check to create .NET (or even Win32) applications?
That "check the Universal box" argument doesn't help a lot of cross-platform developers.
I'm not sure I understand what you're saying. Building an OS X app as Intel-only doesn't make it any more helpful to cross-platform efforts. It isn't any easier to convert an Intel based Cocoa app to a .NET app than it is to convert a PPC Cocoa app to .NET - there should be no source code differences, and even if there are any, they don't just port to .NET or Win32. The whole application is written in a different framework.
What I'm saying is that the posters who say "Adobe are idiots, why don't they check the UB option in Xcode" are clueless about large scale cross platform development and quality assurance issues.I'm not sure I understand what you're saying.
What I'm saying is that the posters who say "Adobe are idiots, why don't they check the UB option in Xcode" are clueless about large scale cross platform development and quality assurance issues.
For an OSX-only application that's already using Xcode, it's relatively easy to build a UB. (There's still the QA problem, but you can build it easily.)
If the codebase is non-Xcode, and has significant x86 optimizations, then I'd believe Adobe's claim about not porting new products to PPC.So you're just talking about not Adobe not wanting to QA the app on PPC?
That makes more sense I guess.
The flood will occur when the bean counters decide that the added cost of building, QA and support for the PPC build is less than the revenue (less profit margin) from PPC sales.And if that's the case, that supports my theory that this isn't necessarily a harbinger of a flood of Intel only apps to come.
Honestly, I think a lot of his response is BS.
Unless they are doing a lot of performance tuning directly for Intel, and so they want to avoid using Accelerate.framework (which can't take advantage of all of Intel's features because it also has to translate to PPC, so it only focuses on what instructions the two platforms share), they really aren't gaining any kind of "streamlined" development by avoiding using Apple's Universal Binary guidelines.