An interesting way to let people know your site isn't XHTML valid.

Basically, it's not a crime for your websites coding to be XHTML invalid. I have my reasons, other people have theirs. My reason is at the time I've written this article, Monday September 17, 2007 taking the extra time needed to learn, write, and ensure X HTML validity doesn't seem to be worth it. It also doesn't seem to offer any obvious benefit, though I'm sure if I did some research I'd find something.

From what I gather, it's a standard created so articles, webpages, and content in general on the web displays properly. I think this is great for new programmers, so they don't have to go through all of the mistakes I did when I was first starting off to ensure website usability across multiple platforms (browsers, OS's) and for the visually impaired.

Basically though, the programming I do works and I've learned that through probably over 8 years of experience. I started coding in high school for gaming "clan" websites, or team websites.

Some may say my style of coding will eventually be phased out, and it may be less the learned way of coding, but I doubt it will no longer be usable. I feel about 99.8% certain that it will continue to be as usable many years from now as it is today, so long as there's no catastrophic disasters (cough cough, man). Why am I so confident that it will sustain usability? Because there's at least billions, probably more than trillions of pages on the internet, most of which will remain unchanged for a very long time who will likely never conform to changing standards. Are the creators of operating systems (OS) and web browsers going to discontinue support those millions, billions, and trillions of websites? It's not very likely unless it's on an extremely limited platform (currently, handheld devices).

To end this article I'd like to provide a link on an image to a webpage which inspired this article and seems to paint a good picture of the very spirit of what I'm saying.