y2k1981: Why would somebody want to choose xHTML over HTML, is it just because xHTML will eventually replace HTML, or are there other reasons?
You know, you could reverse the question: Why use HTML when the combination of XHTML and styles provide for the vast majority of user needs?
Then, the answer becomes obvious: you use HTML when you believe that there is something you must do that isn't do-able using a combination of HTML and CSS, or some other tool.
I'm pretty happy with the direction things are going with XHTML and CSS, so I tend to code toward that and I haven't yet run across anything that wasn't somehow possible. But, as Rick pointed out, there are still a few folks with browsers that won't fully support CSS.
So, what to do?
I code for XHTML+CSS, but I also code with an eye toward older browsers. I run an early version of Netscape (4.7) just so that I know what the site'll look like in an older browser. Sometimes, I find ways to fit everything in very pretty. Sometimes I decide "Well, it's not worth it to make this look beautiful for Netscape 4.7 -- it's functional (and functional in Lynx!), so I'll settle for that".
But see, most everything I code, I code as simply as possible because I'm a stickler for accessibility. I've coded sights for blind readers and this is very important for me. So it's easy to avoid all the doodads and geegaws because my blind readers can't see 'em anyway and it doesn't feel right building a site that excludes blind people.
Cheers,
![[monkey] [monkey] [monkey]](/data/assets/smilies/monkey.gif)
Edward
"Cut a hole in the door. Hang a flap. Criminy, why didn't I think of this earlier?!" -- inventor of the cat door