Flash & Markup: There Is No War
Preface: I have decided to use the term “Markup” to mean HTML5 and to continue to do so here on out. Markup referring to HTML, JavaScript, CSS, PHP and other elements used to create web and desktop applications, games and sites. The term “HTML5″ is too much of a buzzword that seems to be misunderstood by many, including some of those in our communities. I also use the term “Flash” to refer to the entire Flash Platform including Flash Player and AIR.
For the past several months there has been much discussion and debate over web technologies. Some claim Markup is a “Flash Killer.” Some say that Flash shouldn’t be on the web any longer. While others say Flash isn’t going anywhere. At times it feels like an all out war.
Let me make one thing very clear: There is no war.
There is no “killer.” It’s all simply media propaganda.
Flash and Markup have been living comfortably together for over a decade now. Each having their own purpose, their place and use on the internet and beyond.
But technology goes further than simply coexisting. Technology is an ever-evolving virtual ecosystem where components of the environment symbiotic and drive each other to advance, grow and change. And that is exactly what is happening right now.
Markup first was able used to display images (gif, jpg, etc.). Then people wanted to animate graphics. So Future Splash was created. Then people wanted to display video in the browser, and the technologies emerged to do so. Over time more technologies have been created to enable developers and designers to create engaging experiences for their users that hasn’t been possible previously. Some technologies became more widely used than others. But they all live within the same . That doesn’t mean one has been “killed” by the other. In fact, it is quite the contrary.
The better that Flash gets, the better Markup will become. And vise versa.
Take in consideration the <video> tag.1
Video on the internet is rampant. It used to be that you would “need” Flash (or another plugin such as Quicktime) to display video in the browser. But with up-coming Markup you can display video without the need to use Flash. If all you need to do is play video than <video> is great.
Does that mean Flash is going to “die?” No. By no means.
If, for instance, you need to do more with that video than just display it, like add cue points, track data, or create interaction embedded within the video then Flash is perfect for you.
Does that mean Markup will “die?” No. By no means.
Each one will drive the other to evolve and become better. Flash, Markup, and other languages and plugins will continue to change, continue to progress. This is what we need. And this is what we need to focus on.
Currently, varying browsers don’t use the same video codec and they don’t all render the same code in the same manner. This is a problem and is very frustrating to many designers. This problem will eventually be alleviated through progression, through pushing for change but only if we focus on it.
So let’s focus on progression. Let’s focus on making a better web instead of on disputing what component is “better” than the other. Luckily we have the choice to create whatever we want for the web with any tool that we want. We should embrace it, and each other. Let’s have fun and make some awesome work together.
Because there is no war.
I agree, I’m not a fan of lumping emerging web technologies under the HTML5 banner, but to call CSS, PHP, and HTML “Markup” (with a captial M) is more misleading than calling web technologies “HTML5″ to me. Markup (lowercase M) is language defining structure. HTML markup doesn’t *do* anything. It doesn’t *show* images (“Markup first was able to display images (gif, jpg, etc.).”), it more accurately indicates to an interpreter (e.g. Firefox, Safari, IE) that an image should be rendered. How that image is displayed is dependent on the implementation of the browser vendor. This is why we have standards (and why we have to test every bloody browser version for websites and not Flash). Because if browser vendors don’t adopt said standards, we may end up with more IE6.
HTML5 is about semantics and interoperability; it defines a recommendation about how HTML producers should produce documents. If browsers adopt these standards, it will make it easier for producers to create interoperable content that can be consumed sans plugin.
This is why you love Flash; because it’s standards are implemented by the same people who “wrote” the standards. It behaves the same cross-platform (mostly) because it’s a plugin. The primary intention of HTML5 is to reduce the need for plugins, so in actuality, this is a fucking war!
Sure, Flash is ahead in many features, but do not doubt the ability of browser vendors to catch up *very* quickly.
At the end of the day, I am going to continue to use the Flash plugin to add rich content easily in the next 5 years. I like Flash; I don’t even mind the plugin. So, I totally agree with you that it’s not going anywhere. Can we please not call web technologies Markup please though? All I ask.