While I agree with much of this decision, and understand the issues surrounding it, I’m rather bummed to hear Adobe sound like they are “conceding” in this manner. All this talk just continues to blur the really story: (1) Flash does not run well on mobile devices yet. I like my Android devices, but I try to avoid Flash content because it’s not that great of an experience – I’m not sure why Adobe can’t focus on improving this, this would be huge if they could. At the same time, (2) HTML5 not going to save the world next week like Apple loves to say – it’s still a long ways from being a reliable alternative itself. It’s great that Adobe is working on new tools to support HTML5 authoring – that will be great, just sad that it has come to this “feud.”

I’m hoping the performance will improve as people learn to optimize for this new device. Then again, wasn’t that the point of HTML5? It’s supposed to be open and run everywhere (HTML5 is supported).

My friends on the web team at Apple,  helped create one of the first uses of HTML5 video tags on a production site. The HTML5-video-fied videos are for the new iMac and Magic Mouse. Using a non-webkit powered browser, you’ll see the original QuickTime version. This is actually pretty significant when you think about it on the scale of apple.com. Accomplishing this for a site like Apple.com, with all the technical, logistical, and political hoops that must be attended to, is a big accomplishment. Congrats guys!This got me thinking more about HTML5, which, admittedly, I’ve only been watching from afar. I found this summary off some of the new features:1. Web workers. I don’t really get the naming of this, but it’s cool! Basically, the ability to create separate background processes that can run without bogging down the performance of your webpage.2. Video. Embed video without plug-ins as just done by Apple.com….but what about the codec?3. Canvas. Some people don’t see the value of this, particularly if you only reference the example given here. But I can appreciate the potential.4. Application Cache (probably most interesting to me) Store content for applications locally, without needing to beonline and connected to a database on a server somewhere.5. Geolcation. Location information  - via GPS, IP, WiFi, RFID, Bluetooth.