It's still unclear whether having Flash is better than not having Flash.

Click to Flash is the ideal middle ground for mobile devices. Only play the Flash when the user explicitly requests. 90% of the time, the user won't notice the Flash missing, the other 10% it is available on request. That solves the battery issues and the annoying advertisement issues.

For me, this seems pretty simple: if it is shown that Adobe can create a version of Flash that alleviates problems with poor battery life and terrible performance, obviously it will be "better to have Flash". So long as those problems persist, Flash seems like a lot more of a liability than an asset.

I think there are five major points of failure for Flash on tablets.<p>1. Flash integration into system battery management.<p>2. Software support for hardware acceleration, both for video, 3D, and 2D.<p>3. Flash objects' use of network hardware.<p>4. Flash memory caching / swaps.<p>5. Android allocation of processor usage for Flash VM.<p>Implementing a Flash VM that doesn't crush your battery requires addressing all these points. This will be especially hard to support the plurality of hardware and OS varieties.

I really thought I'd miss Flash for certain sites, but it turns out that if it can't be done with html5 then there's usually "an app for that".

I can't stand the middle-ground of things 'sorta working' I would rather have it be either fully functional or non-existant.

I think that the big news with Flash 10.2 is that it does have hardware acceleration for video. <a href="http://blogs.adobe.com/flashplayer/2011/02/flash-player-10-2-launch.html" rel="nofollow">http://blogs.adobe.com/flashplayer/2011/02/flash-player-10-2...</a> The article suggests that 10.2 is not hardware accelerated.

This is what will determine RIM's fate in a few weeks, if playbook flash is just as bad then they are pretty much done for.

Reading that article I could almost hear Steve Jobs over my shoulder saying, "I told you so."

I think flash is just a stopgap until something faster and native comes from android. Both MSFT and AAPL are not supporting it on their mobile platform. Android only supports it because they don't have any other options.