This content has been marked as final. Show 3 replies
I think Adobe should be carefull in not extending AIR/Flex into all development areas. Some software projects are clearly not suited for AIR/Flex, and I think it should remain this way, or otherwise the clean and elegant model may soon be "poluted" with to many different things. Like a swish knife that does everything, but usually not as good as a dedicated tool.
I currently see AIR/Flex as a replacement for the current AJAX interfaces that tries to mimic the desktop interfaces of our everyday OS. We need these kind of interfaces for many types of applications, and I think there is also a big need for it in the future, as we will base more and more applications in a distributed fashion, where we can take our environments with us anywhere.
I've been working with AJAX long before the acronym was invented, and I can only say that it is scary how much work it actually requires to do even basic things. Besides, it's a model that is weak in many areas, like execution speed, cross-platform, browser artifacts, standardisation, etc.
I think AIR/Flex has a great potential to develop into areas beyond my imagination, though I hope that Adobe will be very carefull in what they do to avoid spending time on areas that is better suited for other environments.
So for the time beeing I see AIR/Flex as an AJAX killer, though it would be very critical if you marketed the framework as such. Many of the potential developers are still very pleased with their AJAX skills and applications, and they probably don't like the idea of killing those (yet). This is also why Adobe tries (very hard) to bridge the gap between Flex and AJAX - though in reality it would probably be easier to just trash the AJAX parts.
Adobe created printers with their PostScript engines, and all we need now are monitors and TV sets with AIR/Flex engines - imagine the posibilities then ;-)
Just to be clear, we're not trying to kill AJAX or replace it with Flex. We believe that AJAX, Flash and Flex are all valuable tools. Which ones you choose to use depends on a lot of different factors, including what you're trying to build and the general ecosystem in which you're developing.
With AIR, what's important is that you can continue to use the skills you have developed on the web to build desktop applications, whether those skills are AJAX, Flash or Flex.
In fact, you may also choose to mix and match which you use depending on what you're trying to do. For example, if you want a nice interactive animation inside a Flex application, you can use Flash for the animation (using the familiar timeline and animation tools that designers are comfortable with) and the powerful object-oriented Flex components to connect your business logic.
We will continue to look for ways to improve and enrich the AIR platform, and we will be very sensitive to doing so in a way that will maintain the platform simplicity and expressiveness. In some cases, we'll look at building additional frameworks on top of the core platform, so that the core platform itself can remain simple, while layering on top of it additional functionality for those who need them.
And to be clear too - I know it's not your mission to kill AJAX.
What I mean is that everything you can do with AJAX, you can do with Flex - plus 10 times more, and 100 times more elegantly. Thats why I see Flex as an AJAX killer, though it's up to people to make their own decisions/judgements on what technologies they want to use (there's room for everybody).
Of course you don't switch a big AJAX implementation overnigth in favor of Flex, but it sure would be a great idea in the long run.
I would never base a project on both Flex and AJAX, unless I'm forced to by some circumstances. I would rather work in a direction of replacing the AJAX parts.