Web Design – Adobe v HTML5
The story of the Internet has always been a battle between the old guard corporations and the new guard users.
So, Microsoft has had to battle against Free and Open Source software, IBM had to battle against the PC clones, Apple had to battle against the PC, proprietary Unix had to battle against BSDs, and so on. remember DEC? The Digital Equipment Corporation once ruled the computing world with the PDP and the VAX throughout the 1970s. But time goes by and progress marches on.
What’s bizarre is that corporations don’t seem to learn from history. Adobe, which has already had to fight for its survival when the free image-editor Gimp has risen to challenge Adobe’s flagship cash cow Photoshop, now finds itself at odds over its second most-lucrative business, Flash. HTML5 is coming, inevitably, and there’s very little that Adobe’s proprietary Flash platform can do that HTML5′s canvas element can’t.
Ajaxian covers the whole story better than most. It’s funny that Adobe felt the need to have a seat at the W3C standards table in the first place. But anyway, the prevailing wisdom is that Adobe has been blocking HTML5′s standardization right and left, a charge which they adamantly deny.
In fact, HTML5 aims to reduce the need for all proprietary plug-ins, be they Adobe Flash, Microsoft Silverlight, Apache Pivot, or Sun JavaFX. Interestingly, the HTML5 editors are Ian Hickson of Google, Inc. and David Hyatt of Apple, Inc. Hmmmm, can we think of two companies which have locked horns with Adobe in the past?
Peter Brittain
Web Design Perth
Related posts:
3 Responses
Hi Pete,
When it comes to Flash vs AJAX I would expect nothing less than FUD to be sprouted from the mouths of Ajaxian.
FWIW Adobe has been a fan of standards and open source initiatives for a number of years (opensource.adobe.com). Just because they have chosen not to open source Flash Player (for a number of reasons) doesn’t mean that they don’t have anything valuable to contribute to the developing W3C standards.
Whilst it’s true that HTML is aiming to reduce the need for all proprietary plug-ins – it is still a LONG way from actually achieving any of this (regardless of what Steve Jobs or Google think). For a start, the standards haven’t even yet been ratified. Add that to the roll-out/adoption by the various flavours of browsers, combined with the lack of ANY backward compatibility/support, and HTML5 is in for a long, hard ride.
One of the most rational, and open discussions i’ve seen on the on the whole Flash Vs HTML5 debate was over at CNET-TV Reporters Round Table (http://cnettv.cnet.com/html-5-vs-flash/9742-1_53-50083273.html)
Cheers
Matt
great analysis Peter! and you explained it well (as well).. thanks for taking time to share
You learn something new everyday. I guess the modern uses Flash are becoming obsolete so they are trying to save their skin?