Linked by Thom Holwerda on Thu 28th Oct 2010 22:55 UTC, submitted by poundsmack
Thread beginning with comment 447606
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2005-07-06
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.