Seems to me that there are really two points to be made here: 1) Flash as it is currently implemented is for the desktop. 2) Flash for mobile (10.1) should re

Seems to me that there are really two points to be made here: 1) Flash as it is currently implemented is for the desktop. 2) Flash for mobile (10.1) should really be called FlashMobile 1.0 and will need a lot more time and development to give mobile users an optimal experience. This will also require Flash developers to code for mobile. With regards to 1) It is extremely powerful and can create sites/services/applications/designs that cannot be viewed on a mobile device. This aspect does not negate its value. And with regards to 2) that's no different from many websites you visit in a mobile browser and they are not optimized. Just try visiting HN on an iphone. Brutal! But load it up through Google's mobilizer (http://google.com/gwt/x= http://google.com/gwt/x=) and it becomes actually manageable. So now, who is to blame? Adobe? Nah. They just need more time to advance the mobile Flash code. The Developers? Nah. They just needed Adobe to come out with a decent mobile flash platform and now will need more time to optimize for it. What is really to blame? Impatience. People see shiny "smart" phones and think they should do absolutely everything right out of the box just like their 17" laptop does. These things will come in time. (ahem, that said, I've no issues with all the flash sites that work beautifully on my netbook... that cost half what an iPad does).