Because these libraries handle the browser dependencies, as well as the details of the ready-state handling, I never write Ajax applications without using one of them. It just makes no sense to write all that low-level code when these libraries do it so well and so easily.
this book have one chapter on "Open Source Ajax Toolkits" is this like introducing this toolkit to using for Ajax development?
Note that ICEfaces (discussed in the Drag and Drop chapter) is now open source as well. ICEfaces allows you to transparently add Ajax to JavaServer Faces applications and provides support for Ajax Push.
jQuery is another very useful library that is rapidly gaining admirers and supporters. It only seemed fair to give readers a taste of more than one library so that they could choose which better suits their needs.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
Originally posted by Stan James: Authors, what's your take on the readiness of these libraries for picky corporate users?
Some of them are quite ready; in fact, some are even developed by picky corporate users! GWT is of course created by Google; if they're using it, they're probably getting some kind of benefit out of it. OpenRico is actually created by Sabre for their own purposes.
Should GWT give me better warm and fuzzy feelings, just because Google seems to be Very Smart People?
Seeing as how I work for Google, yes, you should get very warm and fuzzy feelings