Saving Bandwidth With Standards-Compliant Code

RadioheadKid writes "DevEdge has an interview with ESPN associate art director Mike Davidson. In the interview Davison talks about the decision to switch to a standards-based, non-table layout. The interview touches on the process he went through to make that decision and the rewards in both bandwidth savings and browser compatibility. An interesting read for those who have not switched to a standards-based, non-table layout. (hint, hint)"

Comments

bandwidth savings more myth than reality

[larry bagina]

We use mod_gzip for the "non-standards compliant" Work Complaint Center. We tried using xhtml + stylesheets in a mockup, but found that the redesign time would be enormous. Additionally, our logs show most of our readership uses older browsers, and we can't force them to upgrade. Furthermore, the bandwidth savings were minimal.

I like using xhtml and css, and use it for my own personal web pages. When you're going for a larger audience, though, you are limited by their constraints. (Insert MS Windows joke here)