Technology Round Table Podcast #2 - AJAX Frameworks

Last week I posted the first in a new podcast series with K. Scott Allen (a.k.a. OdeToCode), Scott Koon (a.k.a. LazyCoder), and Kevin Dente. We got some great feedback, but we decided to ignore it and continue the podcast. So here's another one!

But seriously, this one's a lot shorter (too short?) and you'll hopefully find the sound quality's improved. We've also heard from several people that, while it's easy for a group of geeks to criticize anything and everything, that doesn't necessarily transfer into useful information.

Show #2 - Topics

  1. Google's announcement that they'll host several popular AJAX libraries
  3. AJAX Control Toolkit
  4. Misc. IE8 issues, including changes to how they'll handle JavaScript loading


Here's our temporary podcast feed. This is temporary, we'll get this on Feedburner when we've got the website set up.


Technology Round Table #3: Should developers learn C? + TechEd 2008 Announcements


  • I think it may have been a little *too* short this time, Jon. For me personally, somewhere around 40 minutes is a good length.

    Forget red/green/refactor - this is long/short/rerecord! :)

    Looking forward to episode 3.

  • I will be an ASP.NET MVC adopter and (hopefully) won't have to touch The ASP.NET AJAX Framework again. ASP.NET AJAX has been pulled out of all the projects I've worked on due to it's poor performance. In the end we've used Scriptaculous or jQuery.

    What's wrong with ASP.NET AJAX?

    Lets look at a case study ( / Dojo), this app was initially designed to include everything and the kitchen sink - performance was an after thought, you know, after they got the sink in there. However, they ended up re-writing the app with performance as a higher priority. Performance in the web browser is one of the places that performance / optimization still matters - it's all about the User Experience.

    Another case study: ASP.NET AJAX. This framework was designed to include everything and the kitchen sink (to give ASP.NET AJAX), everyone was wowed by Update Panels, but... ASP.NET AJAX tries to convert a dynamic language into a static language, it added StringBuilders, String.Format, and other unneeded bloat. The Toolkit relies on ViewState. Update Panels do full-page post backs under the guise of AJAX. ASP.NET AJAX could go down in history as another unneeded exercise in framework / control architecture - it's all about User Experience which is tied to UI responsiveness and performance.

    Great podcast, it really confirms a lot of what I've been thinking.

    I'm a YUI fanboy by the way. :)

Comments have been disabled for this content.