Thanks for making the podcast. I enjoyed listening to your podcast, a few of the subjects stroked a few chords with me as they are issues I have come across.
I would like to comment on the dilemma faced when deciding whether to render ajax called content at the browser or server.
However, when rendering content at the browser, we can save effort on both the server and users internet connection...so what do we do?
An answer can be to simply detect what kind of headers have been sent from the browser and check whether the call is ajax, even an extra get paramater can be provided as it's simple to spoof headers. That's what I do with the framework I have built.
Once the server knows what "path" has been taken to the site, the server can quite comfortably do the processing and send out the same response in a different format. Personally, I stick to formatting such content in XML; I really don't get the whole advantage behind using json.
Maybe you can cover the advantages/disadvantages to either approach some time???