2009
2008
Ajaxian » MooTools and Sizzle
by François Hodierne
Valerio Proietti has written a thoughtful post on why MooTools won’t use Sizzle (and tries to argue why other libraries shouldn’t).
...
I don’t expect every library will drop its own engine and plugin Sizzle right away. However, if done correctly, Sizzle can be an area of collaboration. If it becomes “John’s Library” that is one thing, but you will note that there have already been patches from the Prototype folks and maybe others. Sizzle could be a playground for innovation itself.
Google AJAX Search API Blog: Speed up access to your favorite frameworks via the AJAX Libraries API
by parmentierf & 1 other (via)
The AJAX Libraries API is an attempt to make Web applications faster for developers in simple ways:
* Developers won't have to worry about getting caching setup correctly, as we will do that for you
* If another application uses the same library (much more likely), they there is a much better chance that it will be already caching on the users machine
* The network and bandwidth of the users systems will not be taxed.
2007
2006
Livre blanc : Etude comparative des principaux frameworks AJAX - Livres blancs - Publications - Veille - Clever Age
by Xavier Lacot & 2 others
Cette étude montre les possibilités d’intégration d’AJAX au sein d’applications Web en présentant et comparant 11 frameworks d’actualité : Prototype, jQuery, Dojo, Moo.Fx, Scriptaculous, Yahoo !UI, Mochikit, Rialto, Echo2, Microsoft Atlas et Google Web Toolkit.
1
(6 marks)
