A few days ago, I posted an entry asking why is Adobe entering the Ajax world? I just found this entry where Kevin explains the main idea.

You have to be pretty good at knowing code to use the frameworks. So what we worked on here [in Spry] is how can we get designers more involved in Ajax?
Kevin Lynch
Chief Software Architect, Adobe Systems Inc.

The idea seems to be that Adobe wants to reach designers, not developers. Kevin claims that a designer can use this framework and implement Ajax sites / widgets, thus enhancing the user experience without coding. The Spry framework allows you to retrieve remote dynamic data by using a data binding mechanism, to which some Flash developers are familiar. This approach doesn't fully exploit the advantages of Ajax, and I'm not sure if it even provides any. Can someone think of how a designer could use this framework and why should he even care? I'm not trying to discourage Adobe, this _may_ be a great idea, but I'm blind. I guess I'll have to wait and see how a designer takes advantage of it and show me how Ajax makes him stand above the competition ...

Does anyone have a different point of view?

Ray released blogCFC 5 a few weeks ago but I was hesitant to migrate because of all the custom modifications I've done ... I decided to switch today and overall it wasn't that bad ... my CFC's (xml rpcs, fckeditor, ...) worked without any problem at the first trial, thus the only tedious job was to switch my l&f, adwords, and tracking to the new div/css based layout ... I'm sure I will find something I missed, but I'm really happy with the fact it only took me an hours to migrate. Thanks again Ray!