I had a project (well technically I still do) that the client wanted to be all CSS. It didn't work out. I had it pretty much laid out the way they wanted it, all nice and cool and nary a table to speak of. Then they wanted rounded corners. Rounded corners killed it, and the days I spent getting the CSS just right were undone in 1 hour. That's how long it took to rip all the divs out and do the lay out in tables. INCLUDING rounded corners.
Rounded corners aren't impossible in CSS, but IMO not worth the effort. This is more to do with the browser makers not following the standards, than it is with how CSS SHOULD work. But that's not the point of this post. This post is about why so many in the technology field take a This OR that approach. I haven't written off CSS. It didn't work out on that project, but the next may be ok.
Just so you know where I stand...
Do I think CSS has a ways to go? Yes.
Do I think CSS will eventually make tables a thing of the past? Yes.
Will I keep trying to use CSS instead of tables? Yes.
So now the point. Dave Carabetta posted a while ago about his problems with CSS. Problems I have had too. There are a lot of comments from the CSS zealots, promising a promised land if you struggle through the hard times first... How about this, use tables for now? Why should something so (in principle) require struggle? And not just a day, but a while. I spent days, learning to round corners.... ROUND CORNERS!?!
Kay Smoljak posted about Daves post. Further promising glorious days ahead for those who brave the stormy waters of CSS-P.
Despite all the disclaimers, cross-browser CSS-based layouts are definitely possible and take no more time than traditional table-based layouts. Maintenance and upgrades to CSS-layouts are also much quicker and easier.
That's all well and good, but not true until you've gotten across the "hump".
It's funny that it has to be a "if you're not using CSS, you're myopic" type of thing (which is not what Kay is saying). I see it all the time, "my language, framework, micro architecture, schema is better and anyone who can't see that isn't a professional/isn't looking/is myopic/is not willing to grow.
Blah blah blah!
I'm happy some people have moved to only CSS-P, one day I probably will too. Does my not wanting to deal with such a poorly implemented "standard" make me myopic? short sighted? No and no. Lazy, quite possibly.
When IE and mozilla (at least) can display the same piece of CSS the same exact way, I'll be back. Until then, CSS is strictly for formatting, and some DHTML.