Damn CSS, and damn school.

I remember when I would write a webpage, and just getting it up and working was enough. My first webpage, which has been lost to the electro-ether, was written in a vi session on a dumb terminal in late 1992 or early 1993. It was post-hypertext, but pre-Mosaic.

After my initial forays into the WWW, I was even guilty of using frames upon occasion, and tables and I were practically on a first name basis.

Now, nothing less than W3C Validated XHTML with CSS 2.0 will do. I simply can’t rest until I’ve eliminated every last stray orphan tag, and design elements in the html? Anathema to me.

About this entry

You’re currently reading “Damn CSS, and damn school.,” an entry on Pattern Recognition

Published:: 11.21.03 / 1am

Category:: Personal

4 Comments

Jump to comment form | comments rss [?] | trackback uri [?]

Trish November 21, 2003

Totally not worth it. If you’re going to show it to any potential employers do the nice CSS. Otherwise just slap the project on the Web and edit only if you need to. Sheesh, and you wonder why you feel overworked…
bill November 21, 2003

Gotta agree with Trish here, J. I mean, this is one aspect of my professional job and even I’m not concerned enough to build a 100% validating document. My efforts are better spent developing the product for the university, and taking time to create W3C-approved XHTML with CSS is just masterbation. If it works and looks the same on each platform, it’s a success.
jackson November 21, 2003

don’t listen to them! valid code is just so much prettier. and you can parse it a lot easier too. like when you decide you’re sick of you’re current blog software and want to switch (not that I know anyone who would want to do this… again) back to movable type.
bill November 21, 2003

Still disagreeing: XML validated code is nice up until a point. That point is when you start adding namespaces and other such nonsense that, while great for XML, is kind of pointless for HTML, when most browsers strip it out and throw it away, meaning that all you got by making your code W3C standard is extra transmission time over the ether.

As far as easier to parse, especially in the case of converting data from one format to another, you could just use HTML Tidy to format it proper and then parse.

As far as going from wordpress to moveabletype, if you’re parsing pages, you may want to consider that it is easier to remove the entries/comments/etc from the database that drives wordpress and convert them to the moveabletype tables…

Comment Guidelines

Hyperlinks are automatically generated.
<em>italic</em>
<strong>bold</strong>

Pattern Recognition

Damn CSS, and damn school.

About this entry

4 Comments

Post a Comment »

Comment Guidelines