Here is a good video interview with Adobe product management.
The future is coming!!
It should be very interesting to see the impacts of this.
We started working with Flex a few months ago after trying every viable Ajax RIA framework. We were very reluctant to do this at first as Flex was propietary. There were just too many "pros" to using Flex over any Ajax framework, however. We estimated the cost of development and maintenance of Flex vs. Ajax to be massive. So we went with it anyway.
But now that it is OSS, dang!
Update Changed "We estimated the cost of development and maintenance of Flex & Ajax to be massive." should read: "We estimated the cost of development and maintenance of Flex vs. Ajax to be massive."
4 comments:
"We estimated the cost of development and maintenance of Flex & Ajax to be massive." If you've got the time I would be interested knowing the calculus that gets to massive.
Hi Garrett,
Well it is simple really ... try running the Ajax framework of your choosing on IE 7, 6, 5, and Firefox and see what you get.
Then do the same thing with Flex.
It will work the same with Flex on all of those and on Solaris, OS X, Winders, and Linux too.
So it really isn't calculus ... just dealing with major issues between browsers. You essentially maintain a couple copies of your app. When you talk about testing and maintaining this it isn't pleasent work. Very labor intensive.
Anyways, important to note that this is for RIA development and not adding some Ajax love to an existing app.
Mike
Somehow I was reading your post as saying that Flex had as massive of a cost as developing with Ajax. I get it now.
Quite the contrary! But I see how you read it that way - I updated it to fix that confusing language.
Post a Comment