WiseWeasel, dude, you're all over the place. Like many of the "vs." crowd. I am gonna hit all of your points, so you don't Republican the debate.
ThomPete - you're a voice of reason and contemporary fact.
To the "vs." crowd: try and read all the points; not skimming and then commenting without paying the respect to do some legwork.
* ads - HTML5 ads will exist. The easier they are to make, the more of them there will be. Advertisers will use whichever has the widest audience. In fact, advertisers will be more encouraged by all the circle-jerk mob-mentality surrounding HTML5.
* video playback - for one, HTML5 doesn't play better or with less CPU. I think about 10 or so YouTube videos have proven this (visually, not blog opinion rhetoric). I'd link a few to you, but let's face it...you're not gonna look at them. You'd be forced to see proof. (If you do manage to be overcome with a neutral state of mind, do some research)
* cpu - another red herring. So far, I've not seen 1 canvas+js example (of which has a close equal to a Flash equivalent) that outperforms Flash. I wouldn't expect it to, either, since Flash is compiled and JS is interpreted. Bottomline: an immersive experience is going to take some CPU. Realize it applies to all technologies and get over it.
* ipad/mobile - Flash depletes battery. I agree. Equivalent canvas+js experiences use similar CPU. Taking that into consideration...the battery specifically hates Flash? Please.
* greater control/poor coding - Do I really need to point out that this applies to everything? Not just Flash?
Let's consider that HTML5 is being implemented in 2010. I've been on the 'net since 1995. That's 15 years for video to make its way into the browser -- without the "dreaded" plugin tech.
You know what's dreaded? Not being able to move ahead at the speed necessary to make great, immersive experiences. Being tied to a set of slow, archaically-driven, standards.
Flash (or more specifically plugin arch) is a petri dish for the web's innovative future. It can't and shouldn't die. If anything, it should become more open, more accepted and more accessible.
I'd be fine with it being open. I'm just very happy to see a vendor push website operators to not completely rely on Flash, a proprietary plugin controlled by Adobe. If Adobe were to open up the Flash runtime, I would have zero issue with it, and I'd even wager that Apple would turn themselves around on the issue. To have the entire web at the mercy of Adobe is a bit much for me to swallow. Flash is great at a few things, but websites completely reliant on it needed a swift kick in the pants.
However, I am alright with a website being 100% reliant on Flash just as I am alright with a website being 100% reliant on video. The key issue here is openness, not platform.
ThomPete - you're a voice of reason and contemporary fact.
To the "vs." crowd: try and read all the points; not skimming and then commenting without paying the respect to do some legwork.
* ads - HTML5 ads will exist. The easier they are to make, the more of them there will be. Advertisers will use whichever has the widest audience. In fact, advertisers will be more encouraged by all the circle-jerk mob-mentality surrounding HTML5.
* video playback - for one, HTML5 doesn't play better or with less CPU. I think about 10 or so YouTube videos have proven this (visually, not blog opinion rhetoric). I'd link a few to you, but let's face it...you're not gonna look at them. You'd be forced to see proof. (If you do manage to be overcome with a neutral state of mind, do some research)
* cpu - another red herring. So far, I've not seen 1 canvas+js example (of which has a close equal to a Flash equivalent) that outperforms Flash. I wouldn't expect it to, either, since Flash is compiled and JS is interpreted. Bottomline: an immersive experience is going to take some CPU. Realize it applies to all technologies and get over it.
* ipad/mobile - Flash depletes battery. I agree. Equivalent canvas+js experiences use similar CPU. Taking that into consideration...the battery specifically hates Flash? Please.
* greater control/poor coding - Do I really need to point out that this applies to everything? Not just Flash?
Let's consider that HTML5 is being implemented in 2010. I've been on the 'net since 1995. That's 15 years for video to make its way into the browser -- without the "dreaded" plugin tech.
You know what's dreaded? Not being able to move ahead at the speed necessary to make great, immersive experiences. Being tied to a set of slow, archaically-driven, standards.
Flash (or more specifically plugin arch) is a petri dish for the web's innovative future. It can't and shouldn't die. If anything, it should become more open, more accepted and more accessible.