Linked by Thom Holwerda on Thu 28th Oct 2010 22:55 UTC, submitted by poundsmack
Internet & Networking "Even though its Flash technology is used as a punching bag by Web standards fans, Adobe has been building tools that embrace HTML5. The company recently released its own HTML5 video player, and Adobe Illustrator and Dreamweaver CS5 now contain a number of new HTML5 export tools. Now it seems Flash might be joining the party. At Adobe's MAX conference this week, Adobe engineer Rik Cabanier showed of a demo of tool that converts Flash animations to HTML5 (well, technically it looks like a combination of HTML5, CSS and images)."
Permalink for comment 447606
To read all comments associated with this story, please click here.
RE: Comment by Kroc
by kaiwai on Fri 29th Oct 2010 08:34 UTC in reply to "Comment by Kroc"
Member since:

It’s a tag-soup vending machine! Put your Flash currency in, and out comes tasty tag-soup! ;)

But honestly, why? Don’t Adobe have any confidence in their own technology? What message does this send to Flash aficionados? Why, on one front be pushing HTML/CSS to replace Flash, and why on another front by pushing Flash on mobile? They are losing the plot here.

I don't see anything schizophrenic about what they're doing - Flash is what is going to be in store for the short term but in the long term HTML5 will replace Flash for pretty much everything that it is used for today thus leaving AIR left for their multiplatform application strategy. It is no different to Microsoft who are pushing HTML5 but at the same time leaving Silverlight to be that framework so quick and dirty solutions can be created for enterprise.

Audio/video/usb/printer control/access and numerous other things that Siverlight and AIR have I just simply don't see HTML5 ever acquiring nor do I think it is wise to bloat up something beyond what is absolutely necessary. We already have idiots here who make websites and complain when their pathetically crap code doesn't work with Internet Explorer whilst they ignore the fact that the issue is with their code rather than Internet Explorer. Making the specification even more complex will mean these halfwitts will make even more unreadable and useless websites thus requiring even more 'tolerance' by rendering engines. Keep the specifications simple and get the damn developers up to speed.

As for the Flash converter, as long as the code it outputs can be used on a multitude of browsers then I don't care about tag soup - all I care is about the end result. The issue of maintainability etc. is a matter for the website developer and the parent company to concern itself with.

Reply Parent Score: 5