Anti-Flash Standardistas – You’re Cutting Off Your Nose to Spite Your Face

The more I read attacks on Flash, the more I end up shaking my head in confusion. Honestly, I am a little surprised this is still being debated. People, we need to get over this. Before I elaborate further, I want to make clear my support for web standards, usability and accessibility. Additionally, I understand the concern with Flash – it is not as easy to make accessible compared to HTML/CSS, it has, and continues, to be used for some really stupid things, etc., etc., etc. We have all been down that road, we have heard the arguments. That being said, standardistas: you are fighting a losing battle, and on top of it, a battle not worth fighting. Flash is about as standards-friendly as any media plug-in there is. For each bad use of Flash, there are hundreds being used well. Lastly, and more importantly, it is changing what we can do on a browser and how our generation accesses media. Please, for everyone’s sake, stop griping about Flash and start educating people on how it can be used more effectively with standards and accessibility in mind.

I have been developing with Flash for the last four years. Nonetheless, my philosophy is that if something can be done outside of Flash, it should. In fact, I have written on ways to minimize the amount of Flash used in certain areas. However, due to the fact that HTML was never designed to handle rich media (video, audio, vector-base imagery, motion, etc.), the overwhelming majority of rich media delivery cannot be done on the HTML layer. This becomes abundantly obvious due to the plethora of length tutorials on how to round corners or put a drop-shadow on a rectangle. In fact, I would argue that Flash is the ONLY way to deliver rich media – all other technologies (Windows Media Player, Quicktime, Real, etc.) are not only less pervasive on the internet, they are infinitely less flexible. The whole UGC (user-generated content) revolution would not have happened without Flash technologies pushing the content to viewers. Flash made this happen. Not standards (have you taken a look at YouTube’s HTML?), not AJAX, but Flash. I am not trying to diminish the necessity for web standards or AJAX, but many of the standards-manics seem to have their heads in the sand as to what Flash-enabled sites are achieving. In my opinion, the people that are still clenching onto the archaic notion that Flash is not necessary are diluting the discussion on web standards. Rather than deny its merits and accomplishments, why not work to push it further into the circle of accessibility and standards? No one wants technology and progress to be stifled in the name of standardization.

With Flash you have a plugin in which nearly 100% of users have at least some version of the player on their system. The makers have been working to make the technology much more accessible (can you say the same for Windows Media Player or Quicktime?). In addition, Flash allows things to be done that HTML/CSS/Javascript will NEVER be able to do barring some paradigm shift in the technologies. We hear quite a bit about how Flash is not as accessible as HTML/CSS/Javascript – ironically, the same people that are trying to replace Flash with extremely complex AJAX applications are nearly 200Kb of Javascript for the libraries alone (scriptaculous and prototype are roughly 190Kb combined). I developed the Current TV video player which stands at roughly 54Kb. A more basic and generic version of the same application could easily be under 20Kb. I am the first person to suggest keeping as much in HTML as possible. I am also one of the largest proponents of well-used AJAX. That being said, it is simply obtuse to attempt certain things outside of Flash – here are a few examples:

  • Advanced visualizations
  • Advanced motion treatment
  • Physics engines
  • Projects where visual typographic control is paramount
  • Video or audio playback
  • Video or audio recording through a webcam
  • Rich-media browser based games
  • All of the above occurring simultaneously

Ironcially, when you add up all the traffic from fringe browsers which are incompatible with the highly used Javascript libraries, it comes very close to the amount of users without the Flash player…

I would highly suggest giving Flash a serious second look. There are many new features that offer more accessible-centric options for development and design. Flash 8 and above offers new features for talking with Javascript – giving the potential for all interactive elements to be in standard HTML with Flash simply being the display. The express-install feature allows viewers to upgrade their version of Flash from the SWF on your own site – making upgrading much easier and much less cumbersome of a task. You are most likely going to find a lot of features you did not know existed which open the door to accessibility on the web.

I have no doubt the anti-flash standards folks mean well. That being said, should we not be devoting our energy towards making this technology more seamless throughout the browsing experience rather than pretend that it will just go away? And honestly, if it did somehow go away, would the web be a better place because of it?

The Discussion

24 Comments

  • I was about to respond to one of Rik Lomas’s comments but then i read Rex’s comment and I can rest my case on his points exactly, nice article Some Random Dude.

  • “With Flash you have a plugin in which nearly 100% of users have at least some version of the player on their system.”

    This is simply not true. I’d love to be able to have the player on my system, but Adobe doesn’t make a player for my OS/browser configuration. So basically if your site requires flash, I can’t see it, no matter how many times you send me to Adobe’s web site to download “the latest player.”

    It’s time for Adobe to release the source code to the Flash player as open source so that it can be ported to all operating systems, if this technology is going to be ubiquitous. I think it’s dangerous to allow a corporation such as Adobe or Microsoft to dictate to everyone what operating system or browser platform we should be using. By requiring Flash or some other closed “standard” you are effectively allowing these companies to dictate what OS you put on your computer and how it is to be configured.

    My personal experience with websites that have Flash, when using other people’s computers, is that it is being done simply to provide eye-candy navigation that could have been done using CSS or not at all. Why I need to have Flash just to find the location of a restaurant or see their menu is beyond my comprehension.

  • Gil K – Well said. I’m in the same boat.
    I personally prefer to browse with flash disabled, then enable it for the sites I need it. But for the last 2 years, have not been able to install flash thanks to Macromedia not supporting my HARDWARE. If 64bit processors have been out for 2-3 years, why isn’t the 64bit plugin?!!

  • Increadibly boring and fascinating at the same time.
    Boring: because its just web
    Facsinating: i can see boundless levels of creativity.

  • Flash is often blocked by default due to its use in ads. In addition, I think firefox doesn’t even come with it.

  • Gil K. your opinion is outdated and… well fix your PC.

    Do you know what this means?
    http://www.adobe.com/products/player_census/flashplayer/version_penetration.html

    You are outside the crowd. By the way you probably have a 800×600 resolution, do upgrade to 1024×768 ate least.

    FWA is showcasing the best websites in the world. They’re not just eye-candy navigations. Call it THE new level of experience and interaction.

    Furthermore it’s now 2009 soon it will be 3 years after this post appeared, and yes google has already developed technology to index flash. And you may generate XHTML with everything your flash is loading behind the flash visuals. Check the “Silex” project just an example.

    Flash takes us out of the “square” world of HTML. (Sorry somerandomdude your site is really squary but I do like it)

    As some random dude said, get over this, flash kicks ass and so does the rest. Use all the tools you have at hand to make your great sites.

    Flash, is from what we have in the internet, the closest definition of the internet of the future.

  • you can define xml tags and code an ouput for it in as3.
    then you will have a standardisation like HTML.
    in this case there would be no more search engine problems.
    the question is if you want and if it makes sense.
    because this would mean that there’s only one swf. published by 5 diffrent companies. just like a browser. the difference is that you write applications and not script for an interpreter. you take away half of your tools.

    you have at least one big advantage with flash:
    you can publish on all platforms and all browsers.
    im getting a headache when i have to use css or js hacks for ie.
    i doubt the existence of standardisation.

    ok go drupal yourself.

  • Your wait is over:

    A flash player written entirely in JavaScript:

    http://apcmag.com/Content.aspx?id=5078
    http://github.com/tobeytailor/gordon

    And it’s open source (MIT license) too.

    Which kind of proves the point that Flash isn’t really necessary in the first place.

  • CalDude, are you aware that the Gordon JavaScript Flash Player has the functionality equivalent to Flash Player 1? Do you expect that player bearing the functionality of Flash Player 1 to replace the actual Flash 10? Also, if it reaches Flash Player 10′s functionality one day (if possible) the actual Flash player 10 will be Flash Player 20 by then, and will do things you can’t imagine yet.

    In that little javasript player even a simple tween consumes a ridiculous amount of CPU processing, it’s not efficient, just like those html pages with nice Jquery tweens pushing the processor to the top.

    You can get some nice light animations on the iphone though… :)

1 2

Leave a Comment

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>