jwz: CSS is BS
Steven Canfield: CSS: Where art thou? (Height: Auto)
Jamie’s issue smells to me like someone with a basic understanding of a technology throwing their hands in the air and denouncing the whole damn thing because they just can’t figure out how to do exactly what they want. No one claimed CSS was going to be a walk in the park, but assuming it isn’t capable just because you don’t figure out how to make things happen strikes me as a flawed approach to learning anything.
Steven tackles a much thornier issue, one that as of yet has no sensible workaround or solution. He has obviously tried, and come up short, but that’s no reason to throw CSS out the window.
I’ve never personally laid claim to CSS as being the be–all and end–all of web design. Far from it. The further I probe into what it can and can’t do, the more I realize it was designed with semantics clearly in mind over visuals. There are inherent flaws in the language that probably won’t be addressed for years to come.
However quirky CSS is though, I have to conclude we’re still better off than using HTML alone to solve these problems. Okay, we can’t do everything HTML 4.0 or even 2.0 let us do. But look at how much more we can do that neither of those could. Global style, separation of content and presentation, and reduced download times are huge points in favour of the new.
I’m sure the grass will always be greener on certain issues, but isn’t it nice to have more or less solid CSS support and lament a couple of trivial bits of HTML 4, rather than bemoan the lack of support for CSS while stuck with HTML 4 alone?