As long as Adobe can find ways to help steer an awful lot of what is great about Flash into the HTML5 space (with tools and process to support it), then it's al

As long as Adobe can find ways to help steer an awful lot of what is great about Flash into the HTML5 space (with tools and process to support it), then it's all to the good. I get a bit exasperated reading all the HTML5 boosters who, for understandable political reasons, blithely dismiss flash at a technical and especially domain-specific level. Flash let's me do the following in a browser with relatively clean deployment, like, two years ago: http://www.icecreambreakfast.com/flash3d.html http://www.icecreambreakfast.com/flash3d.html . I'll be ecstatic when I can reliably get the same possibilities from HTML5, but these are real, hard-and-fast features based on specific knowledge about a relatively complicated domain, and often times I get the sense that the domain knowledge issues and feature specificity are somehow beside the point with Flash bashers. At least for browser based games, Flash lets me do a lot of things I want to do right now. It's hard to shake the feeling that a lot of the anti-flash feelings mirror the structure of GIMP versus Photoshop as discussed occasionally on slashdot. I love the idea of GIMP, politically, but taking away Photoshop from me would literally be like partially lobotomizing me.