Web Me Too Dot Uh-Oh

Horse Pooop
Originally uploaded by dcdan.

The first is that it is JavaScript based, as anyone who has written any significant amount of JavaScript should attest to, JS is a pain in the ass for several reasons. It is a scripting language, which isn't bad in its own right, but since the interpreters are browser implementations, this means there is a lot of flexibility and by flexibility I mean that what works in one browser on one platform may (or most likely) may not work on the same browser on a different platform and as for different browsers on the same platform you will most likely run into some issues. Next it is a throw back to the client server days except this time around the client is a random hostile platform on which you run, I have a feeling that XSS attack vectors are now opened daily, this it is assisted by the fact that the JS codes has to be pushed down to the client and in a clear view (a la view source) Another thing that concerns me about AJAX that it breaks the way people currently think about how the web is used, page to page in series sequence like a book. Just when I thought we had finally found away to handle people hitting the back button as an intuitive to get back the lasting thing you were looking AJAX comes along and screws the pooch as the back button can really fuck this model up (I'm looking at you gmail). Additionally pages never finish loading as they are constantly going back and forth to the server, if you think sites that use Flash to navigate are a bad idea AJAX pushes it to the next level as you never leave the page, you don't have a solid link to save. Lastly as shown in this The Daily WTF post AJAX is bandwidth intensive. (and as we have all learned from Ted Stevens the Internet is a series of tubes and they are already saturated)
All that being said, I've launched my new Web 2.0 Startup and I'm looking for good AJAX tutorials especially if they are focused on Java/Struts.