If an advertiser puts non-XML code on an XHTML page, the standard-compliant browser behavior is to refuse to display it. That's not a tolerable situation for Slashdot. That's the main reason.
(We had a long discussion about this a few months back, and 4.01 only squeaked past XHTML by a hair.)
And there are many great reasons to move "part of the way" to 4.01. It makes our development smoother, makes customization for other sites a lot easier (once we provide some tools and docs for that), frees up some of our webhead CPU, lets us start thinking about Ajax, and I look forward to a new stable of Greasemonkey scripts people can write:)
Why html 4.01? (Score:0)
Ads (Re:Why html 4.01?) (Score:1)
(We had a long discussion about this a few months back, and 4.01 only squeaked past XHTML by a hair.)
And there are many great reasons to move "part of the way" to 4.01. It makes our development smoother, makes customization for other sites a lot easier (once we provide some tools and docs for that), frees up some of our webhead CPU, lets us start thinking about Ajax, and I look forward to a new stable of Greasemonkey scripts people can write :)
Parent