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.
Reader Feedback : Page 1 of 1
#10
Utkal commented on the 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 the 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 the 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 the 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 [visit link] , it goes some way to pointing them out.
Don Dodge wrote: D Cheng,
Of course in-house
systems go down. What I
am saying is that our
psychological need for
control makes us hold
onto teh traditional ways
of doing things.
When systems go down we
...
Tommy wrote: I simply do
not agree on many parts:
- .NET has a lot of
traction
- you can
certainly know well (and
master) more than one
language. If you cannot
master more than one
language, this could
po...
Paul Hands wrote: O'Gara
continues to be an
abject, putrid idiot.
Why publish that drivel?
To quote Pauli, "this is
not even wrong". It's
also an egregious
conflict of interest.
/black-pixel.gif){kind=tracking}
.gif)
