So Much Drama in the W3C

For various reasons, I haven’t been able to do much writing for the past few days. (In fact, I really shouldn’t even be writing this.) But I have been doing a lot of reading.

I only recently learned about a big problem with XHTML — that it’s really just HTML pretending to be XHTML in most cases, including mine. Even though XHTML1 is virtually identical to HTML4 anyway, there’s no way I’m going backwards. It seems there aren’t really any particular technical disadvantages to using my fake XHTML, either. It works, and the W3C told me to do it, so why change?

Maybe because now there’s HTML5 to consider.It’s not exactly “done” yet, but browsers are starting to implement its features anyway. Should I jump on board, even though IE is way behind, and things could change? It’s very tempting, but I’m still in the middle of a revamping process as it is. It wouldn’t be the first time I’ve dropped my current progress and started all over again, so my devoted/nonexistent fanbase will start to think I’m a total flake if I keep doing it. Thus, I’m leaning towards no, at least for now. Same with CSS3, for pretty much the same reasons.

Although… I could legally and easily change the DOCTYPE on everything to HTML5. That stone would kill the XHTML bird, and at least injure the HTML one, all without hindering on my current progress.

I’ve also been considering looking into other, more fancy languages, but I don’t have a particular use for anything else at the moment. Thus, I’d probably be better off waiting until I do, so I don’t go distracting myself from current projects to accidentally start another one on a whim. I’ve been dabbling with JavaScript just because I found one specific need for it, but I don’t plan to try anything new with it anytime soon.

Tags: , , , ,

Categories: Contemplation, Meta

Comments are closed.