Monday, June 5th, 2006

Which Ajax Approach Is Right For You?

Category: Ajax, Editorial

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, – 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

3.2 rating from 38 votes


Comments feed TrackBack URI

How a developer with a little self respect can use Atlas is beyond me…

Comment by Hakan Bilgin — June 5, 2006

How a developer cannot at least consider Atlas is obviously not a real developer and has little development experience. I have used 5 different ajax libraries, including my own, and Atlas is by far the most complete and extendable client side library. It is challenging at first, but makes it much easier down the road to create reusable and clean javascript. Although it works outside framework, most .NET developers will use Atlas in the future. We’ll see what happens, but my bet is over 50% of Ajax devs will eventually use Atlas.

Comment by Jim Zimmerman — June 5, 2006

Desinger: select dojo or jquery.
Developer: select jsLINB.

Comment by linb — June 5, 2006

Yingbo, I think you’re going a litle far with the self-promotion in comments on this site. It’s starting to look like spam.

Comment by henrah — June 6, 2006

most tradition business apps also can be improved by ajax technologies, not only “web 2.0” websites.

for example, an ajax auto complete support will be good for “select product” or “select customer” in those apps.

Comment by chenggn — June 6, 2006

I don’t see discussion based around the twin requirements of an ajax framework, ease of control development and ease of control use. All analysis of ajax frameworks should revolve around these criteria, with a heavier weight applied toward the latter.

Comment by Forsooth — June 6, 2006

We all face choices. Thank you Baskin-Robbins for your “31 flavors”. But, there is still a flavor missing. When we use libraries, we should be able to go to any library (of our choice) and look for any “book” to get what we find “good”. Some have started breaking away from the proprietary “framework” type and hype and are offering integration of many libraries into their products. Hopefully this trend will continue and enrich the Ajax choices and experience of many.

Comment by Les Papier — June 7, 2006

I hear what you are saying and atlas is in its beginning stages and is still a little rough, but the new control suite that has come out and how easy it is too extend is going to make it very attractive to exisiting dotnet programmers. I like how they are turning javascript into a more object-oriented language and it has helped organize my javascript better. I really think that when we see the new Visual Studio IDE that will write atlas more efficiently, it will be hard to ignore it as a viable option for any developer.

Comment by Jim Zimmerman — June 7, 2006

Extendibility is already one of the characteristics of an object-oriented programming language, such as Javascript: Mozilla Extending Javascript and Extending Classes with Prototypes
Atlas and their new control suite simply make good use of it. Being experts in packaging, it becomes no brainer to plug these features into their VS IDE.

Comment by Les Papier — June 8, 2006

to henrah:

I can’t find your info. I only give helpful comment to reader on certain article.

Are you admin of ajaxian?

Comment by linb — June 9, 2006

Leave a comment

You must be logged in to post a comment.