Interesting Ars Technica forum post by eVITAERC on some of the complexities that Flash acolytes don’t get when they complain about the lack of Flash support on iPhone and now iPad.

How are the Flash advocates out there suggesting to solve the interface problems anyways? The two biggest uses for Flash right now are:

• Video
• Games

The first one of which is in a state of flux. With HTML5 support and YouTube already a non-issue I’m gonna call this one on the road to solving itself.

That leaves games. How the hell are Apple going to emulate all of the following common Flash game mechanics:

• click
• drag
• keyboard

while clicking is fairly trivial, implementing drag and keyboard presses seem hopeless to me. Is Flash supposed to tell Safari which keys to pop up? What about a whole keyboard that pops up to take up 1/2 the screen real-estate everytime you click on a Flash object? How can Safari tell between, say, a game or a video player flash applet? There’s nothing in the API that can be used to distinguish the uses of the Flash apps. Changing that would require every Flash app on the web to be re-written. Besides, Flash is designed to be device-agnostic.

The iPad is not exactly built for device-agnostic tasks.

Except for maybe web browsing.

Actually the device is tailored for web browsing, so scratch that.

I simply can’t see Flash doing well at all on a tablet situation.

Don’t get me wrong — Apple has an ideological problem with Flash. And, as someone who does web standards, so do I. But it’s clear that Flash is problematic for more reasons than corporate rivalry.