I don’t even remember why I chose XHTML over HTML. Possibly I thought it was the wave of the future. Or maybe I thought all the cool kids used it. (Not really. :))

I guess I started using XHTML about five and a half years ago (“validation”). I didn’t even know what it really was! I still don’t. People commented on Jeffrey’s blog about the extensibility of XHTML, and while I’ve heard the term before, I never knew exactly what that meant, and I still don’t.

I know a little about XML; I had to do a small XML project for school and I thought it was nifty. (Although in my major it was more about JDF files, or job description flows? Something like that. A file that would travel with printing jobs and would contain information about how to print said job.) But beyond that I never got into XML and this extensibility gig. I didn’t understand how XML changed or could even make a difference with HTML.

Because of that, I’ve come to the conclusion that I really shouldn’t keep up with something that I’m not using to its fullest potential (and I should definitely take the mention of it off my resume o_o). All the work that I’ll have to put into removing trailing slashes from every webpage I wrote (including inserting some code into WordPress headers to strip the slashes out) is not a good enough reason for me to keep using XHTML.

I’ll get right on that. After I finish moving all my protected blog entries to a private blog, after I retag and recategorize all the remaining entries, after I tag all my Livejournal entries, after I tag all my dreams, yup. (Some projects that I’ve been working on for ever.) At least I’ll have a few years before HTML5 becomes a reality and I have to buckle down to transition to that.