Monday, June 5th, 2006
As Ajax is developing, different “parties” are forming in their development methods. Some developers prefer to stick with the smaller libraries they know and create their apps there, while others are looking to big players, like Microsoft’s Atlas, to provide them with powerful environments to create next-generation applications.
Dion Hinchcliffe noticed this as well and has written up some of his thoughts on how developers out there can choose the process and products that are right for them to work with.
I’ve been thinking a lot lately about the various approaches to developing Ajax software and trying to construct an intellectual framework for evaluating them. Clearly, a large amount of online software in the future, both SaaS and Web 2.0 (and yes, there’s a difference) will be developed using Ajax. And figuring out which direction to take for now is actually getting harder right now, not easier.
He mentions the different players on the field – Atlas, Backbase, Laszlo, Dojo, Script.aculo.us – and where they fit in. His main point, however, is that, despite the work being done to simplify Ajax connections and applications, it doesn’t matter what you’re using if you aren’t really careful how you’re doing it. Special care should be taken in these formative days of Ajax development not to create something that could cause more problems than it’s worth, no matter what level of product you’re using.
Posted by Chris Cornutt at 12:36 pm