There are a number of unsettling trends in the world of web development, and one of them is not HTML5. One major one is the number of formerly “credible” web news entities touting HTML5 as the sole and righteous assassin of Flash.

Since [Google I/O][1], a developer conference aimed at promoting and demonstrating new Google technologies and products, there have been a flurry of misinformed, thinly researched articles proclaiming that we should go ahead and start making burial arrangements for the Flash Platform.

I’ve already [touched on this][2] once, before Google I/O, but since the web information giant has openly encouraged the adoption and standardization of HTML5, tech media sites and others who seemingly have been wishing for something like this, have decided to post some of the most incredibly blatant, one-sided, and downright wrong pieces of “journalism” I’ve seen since the 9th grade. Need evidence?

These are just examples from the the first two pages of Google Search results for the search terms ‘html5’ + ‘flash’. It’s getting out of hand. Media companies aren’t researching anymore. If they were, they wouldn’t talk about products like “Flash 4” in the same sentence as “Flex 4” (both of which do not exist), and they wouldn’t try to compare a browser to a browser plugin.

When did this start happening? Why are companies all of a sudden OK with not fact-checking or not responding when the Flash Community and Adobe call them out on their lack of professionalism and unabashed antics? To me, a big part of why this upsets me is that Google and Mozilla are companies that have worked with Adobe, even to this day, to help promote and build on the strong foundation Flash already has ([SEO][10], [Tamarin][11]). With a glimpse of a technology that is indeed very cool, and after at [least 6 years][12] of development and still no concrete timetable for standardization, these same companies are telling us it’s time for Flash to write its will? I don’t think so.

As it stands now, there are still things like [NSFW tags][13] being suggested. Even more disheartening to me is the fact that some of the biggest names in the JavaScript community are suddenly openly heralding Flash’s demise. Why weren’t they taking such a hard stance before Google pushed HTML5 and Apple didn’t put the Flash Player on the iPhone? Do they feel threatened somehow? They shouldn’t.

I don’t work for Adobe and I don’t hate JavaScript or it’s developers. I’m a Flash/Flex developer who loves [jQuery][14] and all of the other awesome libraries that are helping to shape the modern web. I love seeing sites that are built with just plain sexy JavaScript, like [Twitter][15], [Delicious][16], and [Readernaut][17]. It’s fantastic to see that kind of engineering in action! I’m especially ecstatic about the innovation and paradigm shift that concepts like [Google Wave][18] will bring because of HTML5.

Adobe has [attempted ][19]to [put][20] [their][21] [thoughts][22] into the mix, even by showing how the two technologies can [work together][23], but these articles somehow never really get syndicated the way the sensationalized HTML5 pieces do.

A rather disappointing supporting point can be found by looking closely at any of these ‘HTML5 > Flash’ posts. Does a single one of those articles have an interview or comment from anyone who is pro-Flash or works for Adobe? I rest my case. It’s just sad to see the web’s news sources for technology an innovation fall so short. Television and print media lost what little credibility they had decades ago (regardless of which political party you belong to), but now we’re seeing the same sensationalism and blatant one-sidedness from our tech-oriented news sources.

In this case, it’s not about politics or agendas, but for the life of me, I can’t figure out exactly what it is about. I’m just trying to understand, because it doesn’t make any sense why news media sites would push a certain technology and call for another’s deprecation.

A question I would love an answer to is: ‘what did Flash ever do to anyone that generated such blind hatred?’ Now, think for a second before you answer this. If your arguments have anything to do with “splash pages” or “banner ads”, they’re automatically cancelled out by “pop-up windows” and “pop-under windows.” I don’t think those doors even need to be opened. Both sides’ arguments are moot. Now, argue either sides’ case without using any of the aforementioned topics. You can’t do it. Both are AWESOME technologies that came from [the same ECMAScript standard][24].

This is a point people love to conveniently forget when taking sides. It’s a fact. Maybe the paths separated when that standard [was split][25]. Project Harmony may have been the crucial factor that recreated the divide between the two parts of the development community, but this wasn’t Adobe’s decision. Mozilla, Microsoft, Apple, Opera, Google, and Yahoo were the deciding parties. The same companies that are now singing the praises of the Canvas and Video tags that will supposedly eradicate Flash. It should be noted that there was even hesitation to rush into anything from Yahoo JavaScript guru Douglas Crockford, who stated that [the only thing we have to fear is premature adoption][26].

[The Oslo Meeting][27], as it now referred to, was supposed to help bring a unified standardization that would assist in ActionScript becoming more open and compatible with working implementations. The result was quite the [opposite][28], as Adobe was now the odd man out, though some said that it [didn’t affect Flash][29] at all. On the opposite side of the coin, it’s great to see that there are still people who are objective about development, even if that means using Flash when you normally use JavaScript and vice versa.

A perfect example is my JavaScript hero [Jeremy Keith][30], who is renowned for being an expert in several web development technologies. He created the podcast site [HuffDuffer][31] and chose to build the players in Flash. When I asked him about why he didn’t use JavaScript to build the players, he said he was “[just using the right tool for the job][32].” There need to be more attitudes like this in the development community.

Further to the point, Adobe embraces JavaScript in several ways, even after the Project Harmony incident. First, Adobe didn’t force developers to use Flash or Flex when deploying AIR applications. They are free and encouraged to use other web languages, including their own [Spry framework][33]. Also, [SWFObject][34] is now the packaged JavaScript standard for embedding Flash objects in [Dreamweaver CS4][35], [Flash Builder 4][36], and even as a [plugin for Web Galleries][37] in Photoshop. Speaking of plugins, a new idealist group has recently emerged pushing the need for a “browser without plugins.” This really seems to me like a concept that was mentioned in a brainstorming meeting and was never meant to go anywhere, but people ran with it. If that isn’t the case, then why shouldn’t we add a tag in HTML5 if we get rid Flash and all other non-Flash plugins? [This][38] is just the list in my copy of Firefox 3.0.11. I can hear you asking "where are you going with this?"

Well, HTML5 was partly born out of the necessity of a more semantic, meaningful web, and the disagreements on how [MicroFormats ][39]should be handled. Tags like <article>, <header>, and <nav> were designed with accessibility and structured content in mind. To that point comes the question, ‘if we rid the browser of plugins, how will Flash be handled in the browser wasteland of of this post-plugin apocalypse’?

I hate to break some hearts out there, but Flash will not just die the day HTML5 is made a W3C standard (if it ever does happen), and it’s silly to even suggest such an occurrence. What would happen to the countless sites built in Flash and the others that use Flash and HTML together? Users just wouldn’t be able to see them? Think about that for a second. It’s not going to happen. But, honoring the wishes of Google and others, I’ll state this. If we’re all about a browser sans-plugins, making a more semantic web, and know that Flash is not going anywhere anytime soon: I am suggesting that the Flash community make a formal request to the W3C and Adobe to implement a <flash> tag in the HTML5 specification.

If you are in any position of influence at the W3C, Adobe, or any other entity, I urge you to help the Flash community and the future of the web by bringing attention to this matter. HTML5 is coming, but Flash isn’t going anywhere. Spread the word.

Addendum: To head off any questions like “what about a ‘Java’ or ‘Silverlight’ tag?”, I have some answers for that as well. Short answer, yes, no. Now, I'm not saying that just because I'm a Flash developer. I have solid objective reasoning behind it. I think the suggested tags need to be justified before they can be added to the specification. Here are some criteria for nomination:

These are just off of the top of my head, but I think it’s a good benchmark to start with. Let’s try to keep the flame wars out of the comments. Please be professional, objective and support your thoughts with research.

Update: David Tucker has done [a much better job][40] of conveying most of what I was trying to say here.

[1]: (Google I/O)
[2]: (RE: Is Canvas the End of Flash)
[3]: (Webkit and HTML5: The end of Flash and Gears?)
[4]:,1000000121,39655473,00.htm (Opera: Web Standards Could Eclipse Flash)
[5]: (Mozilla Warns of Flash and Silverlight 'Agenda')
[6]: (Why can't Flash be like Firefox 3.5?)
[7]: (Quicktime is the Missing Link for Flash on the iPhone)
[8]: (Could HTML5 Kill Flash and Silverlight?)
[9]: (HTML5 Video Tag Could Render Flash Obselete)
[10]: (Google - Improved SEO Indexing for Flash)
[11]: ( - Tamarin Project)
[12]: (W3C - HTML5)
[13]: (Zledman - HTML5 'NSFW' Tags)
[14]: (jQuery)
[15]: (Twitter)
[16]: (Delicious)
[17]: (Readernaut)
[18]: (Google Wave)
[19]: (John Dowdell - Building upon Untested Assumptions)
[20]: (Serge Jespers - Adobe vs the Open Web)
[21]: (Ryan Stewart - HTML5 vs Flash Versions)
[22]: (John Dowdell - Underpromise and Overdeliver)
[23]: (Mike Chambers - Implementing HTML 5 Video Element using JavaScript and Flash)
[24]: (Wikipedia - ECMAScript)
[25]: (John Resig - ECMAScript Harmony)
[26]: (YUI Blog - The Only Thing We Have to Fear is Premature Adoption)
[27]: (Mozilla Standards Blog - After The Oslo Meeting)
[28]: (Why Does Everything Suck - Adobe Screwed By EcmaScript Standards Agreement)
[29]: (Mike Chambers - ActionScript 3 and ECMAScript 4)
[30]: (Adactio - Jeremy Keith)
[31]: (HuffDuffer)
[32]: (Twitter - Jeremy Keith)
[33]: (Adobe Devnet - Spry Framework)
[34]: (SWFObject)
[35]: (Adobe Devnet - Introducing Dreamweaver CS4)
[36]: (Adobe Devnet - What's new in Flash Builder 4)
[37]: (John Nack - Web Photo Galleriy Flash Detection Script Revved)
[38]: (Flickr - Firefox Browser Plugins)
[39]: (
[40]: (David Tucker -An honest open discussion on web standards and html5)