I was trying to figure out why anyone would want to write standards-based web pages specifically for Adobe AIR. I'm not talking about Flash/Flex or ActionScript development, I'm talking about using regular HTML, CSS and Javascript to build a website, but then shoehorning it into the Adobe Flash runtime. Why would anyone want to do this?
The stated reason is to ensure that you are providing a consistent experience across browsers and versions, the WORA promise again, but for real this time. That way you can provide the same crap user experience to all users, disabling their scroll wheel and all that great stuff that Flash provides so "richly". Gag.
No, what this is about is locking down web content: keeping people from right-clicking images and saving them, safeguarding the sacred goodies. But first and foremost: disabling Adblock to make sure the punters see the ads. Keeping the geeks from personalizing your pages with Greasemonkey, and preventing client-side mashups. As collateral damage, keeping the visually impaired or blind from using their accessibility tools. But most of all, maintaining control. Control at any cost!
It's the gospel of control that Adobe has always preached, but a way of applying it to a whole other set of technologies: the ones that have formed a generation of software that enabled freedom of choice and diversity of platforms and spurred the development of the web. Adobe's other gospel of richness means two things: your page looks rich (shiny, high in fat), and Adobe builds a monopoly and a position of control that they can monetize someday. And that would make Adobe rich.
2 comments:
Well said. Your writing is really good. You should freelance for Slash Dot or someone.
..if only Slashdot paid. I'm not trying to endear myself to that crowd, anyhow.
But sour grapes make tasty vinegar.
Post a Comment