Interesting thoughts. Although I'm not sure they would go through the trouble of creating a Flash to HTML5 translator. Instead, I'm guessing that they'll continue to integrate the more advanced features of HTML5 into their DreamWeaver product.
In either case, I think Adobe's play is as a tool vendor. Where they'll really take a blow is on their server-side licensing with LCDS. Perhaps they can tweak it so that it works with Javascript instead of Actionscript.
I agree with the author for the most part. He makes some compelling arguments for Flash. However, in the long run, I don't think you can ignore the fact that Apple and Google are both pushing HTML5.
That being said, HTML5 itself has its own issues. I've written about it in this blog post:
http://www.virtusa.com/blog/index.php/2010/05/html5-is-it-ready-for-prime-time/
(sorry, not sure of the etiquette in posting a link to my own blog -- just thought I'd provide additional info on a related topic)
Slashdot Mirror
Interesting thoughts. Although I'm not sure they would go through the trouble of creating a Flash to HTML5 translator. Instead, I'm guessing that they'll continue to integrate the more advanced features of HTML5 into their DreamWeaver product.
In either case, I think Adobe's play is as a tool vendor. Where they'll really take a blow is on their server-side licensing with LCDS. Perhaps they can tweak it so that it works with Javascript instead of Actionscript.
I agree with the author for the most part. He makes some compelling arguments for Flash. However, in the long run, I don't think you can ignore the fact that Apple and Google are both pushing HTML5. That being said, HTML5 itself has its own issues. I've written about it in this blog post: http://www.virtusa.com/blog/index.php/2010/05/html5-is-it-ready-for-prime-time/ (sorry, not sure of the etiquette in posting a link to my own blog -- just thought I'd provide additional info on a related topic)