This is an unchanged repost of a ReadWriteWeb post, which in turn only summarises the original article by Jan Ozer which is discussed here:<p><a href="http://news.ycombinator.com/item?id=1181452" rel="nofollow">http://news.ycombinator.com/item?id=1181452</a>
This article seems to miss the point.<p>First, it starts off talking about the iPad and how Flash may not be the CPU hog its made out to be. It then goes on to say that HTML5 is more efficient than Flash in Safari. The iPad runs Safari, in effect contradicting their previous argument about the iPad.<p>Next, they say that Apple could allow Adobe to make Flash faster, all they have to do is open up access to the hardware APIs. Who exactly wants a browser plugin to have low level access to the hardware APIs?<p>Seems kind of ridiculous to say that something else is at work here. Does Apple want to kill Flash? Probably, but even if they didn't want to, they've got plenty of reasons not to allow flash on the iPhone/iPad/etc.
The problem with HTML5 is that it does not provide any better new features of multimedia, but an incomplete alternative to Flash. I would definitely choose HTML5 if I can make something that can not be done with Flash nor HTML4
2010 and i am bound to a company so i can have "proper" video on a web page.<p>Flash VS HTML5 is a no brainer for any sane person.<p>I almost forgot, FU Adobe i use FreeBSD.<p>Good riddance.
HTML is doomed. Flash is way more powerful and installed on almost every computer in the world. Flash also runs almost the same on all browsers, even IE6, where many HTML sites break - another clear advantage...<p>Seriously, this argument is getting old. Chose the right technology for your purpose and use it wisely to prevent CPU spikes, security issues, etc. HTML makes strides forward and so does Flash. HTML is great for 90% of all needs, and Flash fills in the other 10% where you need some more flexibility, play audio, have multiple file-uploads, run it as an Air app on the desktop, etc.