Will, I agree with everything you posted 2 stops back.
However, the note at the start of this tutorial is important. And I’ll try to explain.
I tuned into this site via Zeldman’s book on CSS and web standards (as mentioned earlier Ive been out of the loop for a while). He goes to some length hilighting all the great rewards of separating style from content. Im sure we’ve all read it. This site is endorsed by his “evangelism” & in turn evangelizes CSS/web standards, first by redesign & through the philosophy behind the content & those it links with (Meyers et al).
From there, one does (or am I the only one??) get the sense that CSS is considered superior compared to non-CSS (as I think Luke was pointing out) because of CSS’ affiliation with web standards.
But I notice that people are developing really clever ways (Im only referring here to ideas that roam outside of web standard comliant use: hacks & other tricks that convolute CSS code) of doing things that could be done (or is already done) simpler in other ways.
One must ask the question “Why”? If a way already exists to do something, that is simpler & a more effecient use of time, why try to fix something that aint broke?
There are only two answers within my reach:
1. Because they are CSS enthusiasts who love the challenge. (Something I, personally, IMHO, have no problem with). or
2. Because there is a sense that “if I break the standards using CSS its still somehow within the standards or at least better than breaking the standards using non-CSS”.
I have nothing against innovation, using what suits you & leaving the rest. & its ok to break whatever rules necessary to get a job done; this is a fact of design life, for now. But I dont(or perhaps I do now) understand what seems to be a type of CSS fetishism - that it’s the cool new style & also official & valid due to CSS’ popular affiliation with web standards.