This is a really interesting post that I need to read more into.
[Via [Ajaxian](http://www.ajaxian.com/archives/2005/10/ajax_framework_2.html)]I have been doing a lot of backend work with XMLHttpRequest for my Ajax Tagger Version 2, and I am wondering if I should have bothered. I will look into some of these solutions and see what each offers.
[Matt Harrison](http://panela.blog-city.com/ajax_explosion.htm) was talking about making choices between various Ajax toolkits, frameworks, or libraries.
Their survey discusses:
[Dojo](http://dojotoolkit.org/) [DWR](http://www.getahead.ltd.uk/dwr/) [JSON-RPC-JAVA](http://oss.metaparadigm.com/jsonrpc/index.html) [MochiKit](http://mochikit.com/) [Prototype](http://prototype.conio.net/) [Rico](http://openrico.org/) [SAJAX](http://www.modernmethod.com/sajax/) [Scriptaculous](http://script.aculo.us/) [Xajax](http://xajax.sourceforge.net/) [Sack](http://twilightuniverse.com/projects/sack/)
The world of Ajax libs is an interesting one, as they cover various functionality.
We blogged about the Ajax layers in the past:
NOTE: [Michael Mahemoff also collected framework information](http://www.ajaxpatterns.org/AJAXFrameworks)
I lead the Chrome Developer Relations team at Google.
We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.
Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on web.dev, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.