| It's interesting to see PR in action, especially as Proggit, HN, and several popular blogs have been sounding the HTML5-induced death knell for Flash in the last week or so. Translating the double-speak is actually good fun in this case. With all due respect to Jon Gruber, here is the PR-to-Human translation of this link: The current WhatWG proposals called "HTML 5" have been stirring up a lot of polarizing speech lately Positive attention to new technologies is only beneficial if Adobe has a clear monetization strategy for them. So we will introduce a controversy and try our best to make it "polarizing." It's hard for Adobe to have an official opinion But unofficially, Adobe will do everything possible to undermine the excitement over HTML5 and torpedo it at all cost. whatever this consortium of minority browser vendors chooses to do MINORITY. Get it? Unsupported! Unofficial! What happens if the minority goes away? Don't buy Tucker. Buy GM. seeing what the final agreement turns out to be, and how it is eventually manifested in the world, both are prerequisites for practical tool-making Given that we are a tool vendor, this is the only interesting part. And since we largely control the tool market for our tech, this is a major threat to us. Still, I'm glad that an analyst asked a question about it at the quarterly financial call. Here's what Adobe CEO Shantanu Narayen had to say What a threatened tool vendor CEO has to say is what you should use to form your opinion about a technology and its future viability. I think the challenge for HTLM 5 will continue to be how do you get a consistent display of HTML 5 across browsers The biggest challenge for HTML5 will be the constant undermining from companies that see their current tool strategy and quasi-monopoly threatened, such as us. And when you think about when the rollout plans that are currently being talked about, they feel like it might be a decade before HTML 5 sees standardization across the number of browsers that are going to be out there. If we keep repeating the fear of how long it might take to implement again and again, it will take even longer. Your hesitation equals cold hard cash for us. we still think that actually the fragmentation of browsers makes Flash even more important rather than less important When asked about a potential competitor, I always mention how its rise will make our product more important. Because that's what the board pays me to do. Adobe's about communicating your ideas -- publishing to various channels -- not just about Flash. Dreamweaver, ColdFusion and the imaging tools all benefit from an increase in HTML. Hey guys, remember ColdFusion? ... Guys? Adobe profits from easing communication in general Positive communication about Adobe products. And sowing FUD about competitors. But since Slashdot posters ran the term 'FUD' into the ground ten years ago, you can't use it anymore without being derided. SCORE! Flash is a strong bet for emerging platforms I'm high as a kite. I'm increasingly uncomfortable with calling the WhatWG proposals "HTML 5" though Giving something that might become a standard the appearance of legitimacy is dangerous to our business model. Open standards are the enemy of our proprietary tools. What counts is not a press release, but a realworld deliverable What is not deliverable, for instance, is Flash on iPhone and possibly many other portable devices, which appear to be the biggest growth market/land rush of the next decade. Allowing an open competitor like HTML5 to dominate that market would be fatal for us. Shantanu's last point in there really resonates with me Please give me a raise. this whole "HTML5" campaign will likely benefit Flash, because few remain who oppose the idea that "experience matters" Our experience in making cold hard cash from selling Flash tools matters the most. Using "scare quotes" will help de-legitimize HTML5. Things are quite a bit different than five years ago. We now have a virtual monopoly on serving casual video on the web. We will fight anything that threatens us. iPhone helped to radically increase the number of phones with Flash support The new QuickTime X plays Flash videos natively. We might be screwed. the "HTML5" publicity helps marginalize those few who still argue that images, animation, audio/video and rich interactivity have no place on the web HTML5 uses open standards to play those file formats natively, which severely undercuts our tool/server profits. Flash will be able to deliver on those heightened expectations, regardless of what each separate browser engine does. Fuck you, WHATWG, Chrome, Mozilla, Safari. |
MINORITY. Get it? Unsupported! Unofficial! What happens if the minority goes away? Don't buy Tucker. Buy GM.
The vendors with minority market share are really putting their weight behind this spec, and adopting features as quickly as they can. The majority browser vendor, Microsoft, is not. They have a conflict of interest now that Silverlight is out. MS has displayed reticence in cannibalizing functionality from their other products in the past; IE is unlikely to subsume Canvas and Video features since its the domain of Silverlight ( for the time being ). We have been in this situation before - how many of us have banged our head against the desk for hours fixing a "bug" for IE6? Though many web devs are brave enough to only support current gen browsers, many of us do not have that luxury. I love HTML 5, but I can't imagine any of the features to be "killer" enough to make users switch to more modern browsers. That said, I'm not big on prognostication, and if it turns out I'm wrong, I'll be a happy man.
What a threatened tool vendor CEO has to say is what you should use to form your opinion about a technology and its future viability.
100% agreed. But I also wouldn't discount that opinion just because it comes from someone in a weakened position. Every one of us is a geek, and every one of us has been in a seemingly losing position when we actually know we're right. I'm with you, about not trusting the source, but not on the idea that it invalidates the position of that source.
The biggest challenge for HTML5 will be the constant undermining from companies that see their current tool strategy and quasi-monopoly threatened, such as us.
This I have the biggest problem with, and I'll project onto it some other sentiments I've seen from HN and Redditors, just to make it interesting :) I'll posit this: a monopoly, kept in check with free and open source alternatives, is healthy for our web ecosystem. I'll go further: we would not have AJAX if Microsoft didn't invent it. It's a hell of a good idea, but maybe not good enough, alone, to force users to switch browsers. Since MS invented it, and since it had the dominant browser ( a quasi-monopoly ), and since it was a great feature, other browsers could implement it. We all benefited. If it came from Mozilla, web devs would have been bending over backward to not totally ruin the experience of their AJAXified apps for IE users, and no one would have bothered to switch browsers. I know that I'm picking on subtext from your comment, and that's what I'm most disagreeing with, but I wanted to share that opinion.
If we keep repeating the fear of how long it might take to implement again and again, it will take even longer. Your hesitation equals cold hard cash for us.
Everyone knows that HTML 5 will be faithfully implemented in at least FF/Webkit/Opera before long. But, for right now, IE is still the lynch pin. Adoption of HTML 5 features will occur as rapidly as they're introduced into IE ( if history holds true - I pray for some really feisty and ballsy web devs, but I'm not holding my breath ). This, obviously, sucks, but for the time being, Adobe is right - if we're going to wait for IE, and if IE remains the dominant browser, we're going to be waiting a while.
Flash is a strong bet for emerging platforms - I'm high as a kite
How is this not accurate? I can reliably replicate any feature from HTML 5 in Flash today, and it'll work on any platform I want (* except all the platforms geeks get cranky about ;) ). Those features have been around for a while now. Flash's been a test bed for new ideas, and we all reap the benefits when it fails miserably ( intro movies = suck // never use a monolithic binary model for the web ) and when it succeeds spectacularly ( cross-platform, single-codec video player: <video>; audio player: <audio>; custom fonts; vector illustration <canvas>; animation [ more CSS3 ]; persistent local storage; etc ]).
_I'm increasingly uncomfortable with calling the WhatWG proposals "HTML 5" though_ I'm offput by this statement as well. I don't know why he's uncomfortable... It does seem like he's trivializing it.
Open standards are the enemy of our proprietary tools.
Again, I wouldn't count Adobe out on this one. The <video> tag isn't going to kill Adobe. Proprietary means Adobe can implement DRM. Yes. I know. WE ALL HATE THE FUCK OUT OF DRM. YouTube could thrive without DRM, but Hulu, for right now, could not. It is because Hulu offers protection on their videos ( Netflix, too ) that they're allowed to stream content to us. We could all "send a message" by torrenting those shows, cutting out Hulu/Netflix until they switch to <video> in lieu of Flash. But no one else will. Most people don't even understand what a plug-in is. They don't care that it has DRM attached. And frankly, me watching a few adverts so that the writers of The Office can buy a couple more ivory backscratchers is really not that bothersome for me. Again, Adobe implemented the first successful browser plug-in - they paved the way for <video> in the HTML 5 spec, so while we're chanting for its death, let's not forget that it's done some good.
Fuck you, WHATWG, Chrome, Mozilla, Safari.
Now you're just projecting ;)