Richard Davies wrote: The UK has a good crop of technology pioneers in cloud computing - for example ElasticHosts, FlexiScale, Flexiant, OnApp - and also some strong government initiatives such as G-Cloud.
We will have to see whether this kind of technical leadership converts into swift mass-market adoption or not.
When it comes to rich Internet application (RIA) technologies, application development professionals must choose between two paths: AJAX or Adobe. AJAX is the best bet for experienced Web development shops looking to incrementally evolve existing Web applications. Of course, selecting AJAX also raises the question of whether to go with a homegrown, open source, or commercial AJAX framework.
In contrast, Adobe is best for shops looking to completely transform their Web experiences. But to do so, firms must acquire the skills necessary to use Flex, which is the development framework for the Flash runtime environment. Early adopters with time-to-market concerns and comfort with either smaller vendors or open source can select AJAX with confidence. But firms that require support from a larger vendor and full-featured development tools will do better with Adobe.
App dev professionals should make the selection based on their time-to-market requirements, whether they're looking to evolve or revolutionize their user experience, and whether they prefer tools from large established vendors.
AJAX: The Fast Lane to a Better User Experience App dev organizations that prefer a fast path to RIAs — for developers and users alike — select AJAX for the following reasons:
AJAX helps shops meet time-to-market needs. Developers with existing Web skills find that adopting AJAX involves a shift in design patterns, not a wholesale change in programming language or development tools.
AJAX favors gradual re-factoring of existing Web apps. AJAX is based on open and standard languages like JavaScript and XML. This makes it easy for developers to integrate AJAX widgets into existing Web applications that are written in HTML, DHTML, or server-side JavaScript.
AJAX can deliver speedy performance. Vendors of commercial AJAX frameworks like Backbase and JackBe invest considerable resources tuning their AJAX frameworks for speed because their clients have tiny footprints and download to browsers so quickly that there's no perceptible lag in app performance. Some open source AJAX tool kits share this trait, but others approach the size of Adobe's Flash and have equally long install times.
About Jeffrey Hammond Jeffrey Hammond is a senior analyst at Forrester Research where he covers tools and techniques for application design and development. He is a leading expert on software modeling techniques, integrated development environments and the emergence of new rich Internet application development practices and tools. Jeffrey holds a BS in economics (finance) from the Wharton School at the University of Pennsylvania.
Reader Feedback: Page 1 of 1
#10
Utkal commented on 2 Apr 2008
Hi. What about Curl ? you ve not named curl in your article. Is it so bad that it can not compete with RIA technologies like Ajax, Flex, AIR, Silverlight etc ?
I wish you could ve included Curl too. I'm new to web dev, and started learning Curl. Its easy to understand and learn.
#9
Ted Farrell commented on 22 Feb 2008
Hey Jeff. Interesting article. We have found that our users don't have to choose. Our JavaServer Faces framework generates both Ajax and Flash markup. Other companies (google, etc.) do similar things as well. I think the choice only comes into play if you decide to use Adobe's Flex components, which only generate flash. Many other component toolkits generate multiple formats, including Ajax, Flash, WML, XML, etc.
Thank you for this interesting topic,
Could you please expand this topic with the accessibility possibilities of both solutions ?
In my mind, it seems that Flex does not support accessibility and with some customization AJAX frameworks like GWT are able to handle this major subject (we're currently working on this topic using GWT). Regards.
#6
Gringaus commented on 2 Nov 2007
Just stumbled upon this article... Pretty embarrassing for senior analyst at Forrester Research to come up with this b...t. Forrester, get rid of him, seriously.
You forgot to mention that Flex is object oriented. JavaScript is pseudo-OOP at best. After all these years, are we still debating about whether or not OOP is important? That is crazy!
As already mentioned in the Canoo RIA blog, reading this article is recommended. It lists several issues to consider that many others focusing on mere technical aspects leave out.
Digg this? Dump this you mean! I suggest to use both technologies before writing this kind of articles. Flex is simply the technology to use - if you would have used it you would know.
#2
Andy commented on 29 Jul 2007
This article generated more questions in my mind than it helped with answers.
What about the Flex/Ajax bridge? What about companies that will continue to use both Flex and Ajax for a variety of different means?
What I really need is more useful information on how these technologies help address various types of business problems that are being translated into technical requirements.
What are people's main concerns? Mine are security and performance between the client and server. XML based services can be very verbose, are test show that Flex can have some advantages here, but what are other people finding out?
What are the cost differences?
Hopefully you can address these questions in a follow-on article.
I'm afraid you are wrong on a number of points here. This is not subjective, but mostly factual errors. Have a read of this http://blog.schematic.com.au/?p=46 , it goes some way to pointing them out.
Utkal wrote: Hi. What about Curl ? you ve not named curl in your article. Is it so bad that it can not compete with RIA technologies like Ajax, Flex, AIR, Silverlight etc ?
I wish you could ve included Curl too. I'm new to web dev, and started learning Curl. Its easy to understand and learn.
Ted Farrell wrote: Hey Jeff. Interesting article. We have found that our users don't have to choose. Our JavaServer Faces framework generates both Ajax and Flash markup. Other companies (google, etc.) do similar things as well. I think the choice only comes into play if you decide to use Adobe's Flex components, which only generate flash. Many other component toolkits generate multiple formats, including Ajax, Flash, WML, XML, etc.
Ted Farrell - Oracle Corporation
Gregory C wrote: Hi,
Thank you for this interesting topic,
Could you please expand this topic with the accessibility possibilities of both solutions ?
In my mind, it seems that Flex does not support accessibility and with some customization AJAX frameworks like GWT are able to handle this major subject (we're currently working on this topic using GWT). Regards.
Gringaus wrote: Just stumbled upon this article... Pretty embarrassing for senior analyst at Forrester Research to come up with this b...t. Forrester, get rid of him, seriously.
Harry B. Garland wrote: You forgot to mention that Flex is object oriented. JavaScript is pseudo-OOP at best. After all these years, are we still debating about whether or not OOP is important? That is crazy!
Canoo RIA Blog wrote: As already mentioned in the Canoo RIA blog, reading this article is recommended. It lists several issues to consider that many others focusing on mere technical aspects leave out.
For a detailed discussion of this article, see:
http://canoo.com/blog/2007/08/15/how-to-select-ria-technologies-part-1-o...
Dirk wrote: Digg this? Dump this you mean! I suggest to use both technologies before writing this kind of articles. Flex is simply the technology to use - if you would have used it you would know.
Andy wrote: This article generated more questions in my mind than it helped with answers.
What about the Flex/Ajax bridge? What about companies that will continue to use both Flex and Ajax for a variety of different means?
What I really need is more useful information on how these technologies help address various types of business problems that are being translated into technical requirements.
What are people's main concerns? Mine are security and performance between the client and server. XML based services can be very verbose, are test show that Flex can have some advantages here, but what are other people finding out?
What are the cost differences?
Hopefully you can address these questions in a follow-on article.
Chester Chipperfield wrote: I'm afraid you are wrong on a number of points here. This is not subjective, but mostly factual errors. Have a read of this http://blog.schematic.com.au/?p=46 , it goes some way to pointing them out.
Apache Deltacloud, the Red Hat-contributed ReSTful API that abstracts differences between clouds so services on any cloud can be managed – provided of course there’s a driver – has graduated from the Apache Foundation’s incubator and is now a full-fledged Top-Level Project (TLP).
The...
With Cloud Expo 2012 New York (10th Cloud Expo) just four months away, what better time to start introducing you in greater detail to the distinguished individuals in our incredible Speaker Faculty for the technical and strategy sessions at the conference...
We have technical and st...
AMD said late Tuesday that its chief sales officer Emilio Ghilardi had left the company and that CEO and president Rory Read is going to do his job while a replacement is sought.
AMD didn’t say why Ghilardi left but it’s assumed Read wants his own people. Read is relatively new to th...
During the lifespan of M3 (Monitis Monitor Manager) there has always been something lacking – timers.
M3 execution procedure was outlined in this previous article.
The execution mentioned in the latter was a one-time-execution, whereas server monitoring requires periodic invocati...
Red Hat is putting its bought-in Gluster scale-out NAS storage technology,
acquired in October, on the Amazon cloud.
It’s styled Red Hat Virtual Storage Appliance for Amazon Web Services and
other clouds are supposed to follow in short order.
A new episode of the screencast series is now available at the OpenNebula YouTube Channel.
This screencast demonstrates the new easily-customizable self-service portal for cloud consumers. Its aim is to offer a simplified access to shared infrastructure for non-IT end users. The scree...