I apologize. While I understand the point you are making in the article, I disagree with this statement:
"You can order your content how your like. You are restricted only by your knowledge of CSS and not its ability as a styling language to render your documents. "
I will retract what I've said if you can demonstrate a fluid 3 column layout using only those 3 divs (left, right, center) where the center column expands with the browser, the sides remain constant width, and the order is preserved. This is trivial using tables.
Css tends to show its rough edges when you use it outside of a fixed width or absolutely positioned environment.
Before anyone adds new requirements, consider these ones: it has to be emailed and in the printout, the columns should look like tabs above the midle area.
In all seriousness, sometimes requirements are inane, pointless and unreasonable and you just have to push back and say it can't be done.
I think CSS detractors tend to obsess over specific points that tables can handle normally, but often leave out real life situations where obsessive alignment is not necessarily the biggest of the problems. Bias (in this case towards css vs tables, as opposed to web dev in general) is an interesting phenomenon.
"You can order your content how your like. You are restricted only by your knowledge of CSS and not its ability as a styling language to render your documents. "
I will retract what I've said if you can demonstrate a fluid 3 column layout using only those 3 divs (left, right, center) where the center column expands with the browser, the sides remain constant width, and the order is preserved. This is trivial using tables.
Css tends to show its rough edges when you use it outside of a fixed width or absolutely positioned environment.