Picking an Ajax Framework

| by Scott Delap Follow 0 Followers on May 03, 2007. Estimated reading time: 1 minute |
Dr. Dobbs is currently featuring a case study of the Ajax framework selection process of a development team at T. Rowe Price. The team evaluated a number of popular Ajax frameworks for use in their next generation application:
  • Dojo 0.3.1 (
  • Prototype and Scriptaculous 1.4 ( and
  • Direct Web Reporting 1.0 (
  • Yahoo! User Interface Library 0.11.1 (
  • Google Web Toolkit 1.0 (
After initial review GWT was eliminated due to the legacy team division of UI and back end developer along with the requirement of learning a new Java based API. DWR was also eliminated due to the patch needed for the version evaluated to work with the Websphere Application Server used by T. Rowe Price. This left Prototype, Dojo, and Yahoo UI for continued evaluation.

The case study then goes on to compare how each framework fulfilled the requirements of creating a tabbed ajax widget and a dynamic "hub" widget with a title bar. All three required custom work for the desired tab widget functionality with Dojo providing the closest functionality out of the box. The team then moved on to look at load times:

...The smaller the footprint of the framework used, the less likely performance degradation occurs. The total compressed JavaScript file sizes required by YUI (22K) and Prototype (32K) are significantly smaller than the single custom Dojo JavaScript file, which is about 200K. All three libraries performed well with a high-speed connection; however, the YUI and Prototype/Scriptaculous prototypes performed faster with 56K dial-up connections...

Finally the team looked at overall ease of development. The consensus was that Dojo provided more features and widgets but customization was harder due to the number of files needing modifications. Yahoo UI was ultimately choose due to its well documented code and detailed tutorials on the Yahoo website.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Good comparison... by Mittal Bhiogade

I liked the process how the comparison between different ajax frameworks was done using pugh matrix.. I hope that's what is called.

But in my opinion, DWR is best ajax framework if there are no requirements to have fancy widgets may be just tables on view pages that refreshes asynchronously

extjs by Dominik Dary

why not use a layer above theese frameworks:!

Re: extjs by ZedroS Schwartz

Thanks to Java popularity, I guess we all could speak about another framework, so... Whatever, it's still interesting to read to know more about the numerous existing frameworks.

JQuery by Janos Haber

Ok, but where the jquery?

Re: JQuery by waqas zahoor

i think JQuery is one of the best in business

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

5 Discuss

Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you