[thelist] XHTML overrated (was: CSS, Netscape, .class oddity?)

Jorah Lavin madstone at madstone.net
Mon Jul 24 04:34:20 CDT 2000


At 10:53 PM 7/23/00, aardvark wrote:

>a lot of it boils down to 'code to XHTML because it will
>promote good code'...



>XHTML doesn't automatically *stop* support for HTML, nobody
>can do that...  moving to XHTML is noble, but i don't see
>much beyond that right now...

My take on this... moving to XHTML isn't to support some theoretical 
"stricter" future browser, but to support other user agents such as mobile 
devices, adaptive equipment, and so forth... if your pages are only to be 
seen on the usual "standard" web browsers, then probably there is little 
need to make the switch.  If you think you have content you might want to 
(ahem) "re-purpose" for use in the next wave of user agents, then it 
probably does make sense.

And no... I'm not using XHTML (except a little on my GrokSoup page) but I 
_will_, RSN.

(and if you already are coding to HTML 4.x, then yes, the conversion should 
be easy down the road, and it wouldn't surprise me if there are automated 
tools to do this... as if I'd trust them...)

-Jorah

  





More information about the thelist mailing list