Not quite enough AIR to breath with

  • 15 December

Adobe is really trying to bake something new and fresh like AIR, unfortunately it's doing it using outdated half-products, which can constitute in some really disappointing results.

A few months ago I have given some time into developing a project I came up with – which would be quite useful for many AIR developers – unfortunately while Adobe AIR was still a pretty fresh release I ran into many technical obstacles making it pretty impossible to finalize the output.

Now, a few months later, I’ve given it another go just to find that, even though AIR is now in half-way to reach a completely new iteration level, the obstacles are still there, plus a couple of new ones.

I’m a front-end developer so, quite obviously, what I want to use in AIR is the AJAX-HTML option… Adobe had indeed made some good decisions here, ending up with WebKit as the rendering engine – which makes us front-end developers super-happy. Yet, what doesn’t make us that happy is the fact that Adobe decided to trim-down the available features that WebKit provides us with. That leaves us really little to work with, ergo creating beautiful UI using ie. CSS 3 + the -webkit specific properties.

This brings me to the disappointing results point I’ve mentioned at the very beginning. All of the trimming-down, disabling features seem to be caused by Adobe deciding to use some of their obscure and somehow outdated technologies to deal with the completely new ones – which clearly don’t go together.

Come on Adobe, no opacity support? Really? Please.

In other news: I’m really hooked on Iron & Wine lately.

One response so far. Care to add one yourself?

  1. Trevor Cape December 17th, 2008 at 03:18

Leave a Reply

Fill-in all the forms

Categories