Say, I've got an idea: What if Apple said "Sure, you can release a standalone Flash player on the iPhone, as soon as Flash plugin performance on OSX is on par with Windows. That would be really, really funny to see what Adobe's response was.
PS 10, just like the other Adobe CS3 progs, are not targeted towards Macbooks, Minis or G3 // G4 computers. Use old software with old computers, it's that easy.
Ok, you can argue that CS3 runs ok on a four-processor Mac with 8GB of RAM, but I'm not talking about trying to run CS3 on a G3 iMac or something. I bought an absolute top-of the line MBP 17" in mid-2006, maxed its RAM, and put the fastest 7200RPM drive available at the time in it. CS2 was the year-old current version at the time, but was not Intel native, so ran poorly. CS3, released about 9 months later, would be the first native version available for that pro-grade Mac (portable, but still dual-core and pro-grade), and runs ok so long as it is the only thing running, period. Otherwise it slows to a crawl, even with modest-sized images.
My point isn't that Photoshop is unusable on what was a one-year-old higher-end Mac at the time of it's release--it's not, I use it frequently--just that it's ridiculously resource hungry when there's no obvious need for it to be. Really, what features were added between CS1 and CS3 to cause such a huge performance hit (other than the preposterous activation scheme)?
And poorly-coded Flash ads are only one minor way of exposing Flash's performance problems on any platform other than Windows, they are NOT the cause. Also, any idea why Flash isn't multithreaded at all (or sure doesn't seem to be, based on what a badly-written ad will do when open at the same time as another flash animation)? Is there some technical reason for that?