The links in the top post no longer work, but I think I’ve read this kind of thing before.
I think that Web Standards is a goal. Often a higher goal than "getting a site to work quickly exactly the way the client wants it".
Essentially: Code using CSS elements, but if something is easier using a table, then use a table. This will remain the case until CSS3 is widespread, which I believe has some table-esque stuff going on.
I’m suspicious about the way that the rise in Web Standards and "tableless" design does in many cases coincide with a recognisable "Web 2.0" look which is clean and simple. A certain degree of this may be due to people finding it difficult to align the usual clutter perfectly across all common browsers.
This very forum page uses tables. And why not? It works.
Look at
this Vanilla forums page for example. No tables; it makes designers do things a different way. Is it better? Not necessarily.
I think if you reach a point where you are three tables deep, then something is wrong.
From a MODx perspective, I think that a table in the template is no bad thing - especially as it can be changed later. This is the part that benefits from tables’ stretchy abilities, and absolutely the place that you don’t want to fall to pieces on older browsers. Page content can be rearranged without fear. The "framework" of a complex page benefits from being a table.