You need to do more research before you go on a rant like this.

The iPhone runs on an ARM CPU. The 3GS, in fact, runs on the same CPU found on the Palm Pre. These CPUs do not have interchangeable code with x86, or even PPC CPUs found on Macs.

The reason this is important is that before this Flash Lite movement, there was NO ARM CPU Flash code. All the code running on the various mobile platforms, including the iPhone, would have needed a rewrite. Also, keep in mind that there’s another reason for a rewrite. Without it, performance would be abysmal. Flash Lite, while compatible with 90% of flash SWFs, is not 100% compatible. Some features were reduced or cut in order to keep the mobile platform fast, and easy on battery. It also features entirely new GPU acceleration to help the mobile devices perform better.

Also, you’ll probably find that Flash is not really the culprit with your crashes. I do not see anywhere near the level of crashing you do, and I believe the plugins actually run the same code on PC and Mac now (as they are both x86 CPUs), with small adjustments for the differing file structure, plugin interface on Safari, and GUI.

Perhaps its your Safari causing problems, as I run Firefox on OS X, and I have no such issues, neither with performance nor crashing.

Sandboxing is nothing new, and in fact, Chrome does it for ALL plugins, not just flash. If I’m not mistaken, the same applies to Safari now. That was not implemented soley because Flash is far too unstable, but because it’s more sensible overall. It’s the same reason why OSes in general try to keep one process from taking down the entire system. It wasn’t put in because a certain program was unstable. It was put in because it doesn’t make sense to let one part of the system take the rest down, in general.

Also, to render the rest of this completely irrelevant, my point was that there is absolutely no reason to bring in general Mac complaints about flash over to any edition that would arrive for the iPhone. The iPhone would be running an entirely rewritten set of code that would be completely unrelated to the Mac version, and would actually be the same code running on many devices, including Nokia phones and Palm phones.

You’re simply making a connection where there is none. You need to look at the iPhone in terms of its hardware, not its software. Stripping out the OS layer, that iPhone has little difference between other phones of similar hardware. And that OS layer is not going to affect the plugin, by design.

If for no other reason than because if Flash was available on the iPhone it would be the single-largest installation of Flash Lite 10.1 in existence.

This isn’t the first time that Apple has shown Adobe the door, by the way. Adobe has been hit hard by many changes on the OS X platform with its various CS products. Adobe has been nothing but calm and forgiving over this.

Apple is being unreasonable. Even if Apple is truly afraid of such a problem on its iPhone, it needs only to glance at the list of companies who are behind Adobe on this matter. In fact, it would be easier to simply list the companies who are not: Apple.

Nokia? Supporting. RIM? Supporting. Google? Supporting. Palm? Supporting. The list goes on. Google and Palm have much reason to be afraid, as well. Flash support on Linux has been little more than a joke in the past. OS X, even if you consider your so called commonplace flash issues, is nothing compared to the Linux side. Google and Palm’s new phones all run Linux. Yet they’re both on board.

Besides, what’s stopping them from sandboxing it on the iPhone as well? It’s not like other apps on the iPhone are perfectly stable either.