Here's my contribution to the CSS debate (via email to Dave Winer):
I just went through the pain of attempting to build a table-less site for Watson:
- There are lots of CSS bugs. Each browser has its own set of bugs. The spec isn't simple enough. The conceptual model--boxes--is not intuitive.
- If you have even a small percentage of OmniWeb users, you'll piss them off to no end when you tell them to get a standards compliant browser. Worse, there's no way to tell OW to not attempt to use the css on a page. Worst of all, some OW users pose as other browsers--there's a preference to pose as many different browsers. We ended adding a bunch of tables back into the design to deal with OW's shortcomings.
- CSS Boxes aren't as flexible as tables. They don't adjust to the size of your content as well as tables. If you're doing things dynamically, things break that worked in the nice clean world that you tested it in.
Net-net. Table-less CSS designs are for people with time to experiment, not for busy people shipping product for a diverse user base.