I really feel for the zealwith which you push .css and not tables. But really, that is such LAME zealotry. It's like looking at a toolbox and saying "hammer, you suck. I'll never use you again, and why did I ever? I'll use pliers from now on and do everything with them, not matter what."
Why can't we be *SMARTER* about it and say, tables have their place and css has its place? Make them work together, which is much easier than trying to do one or the other.
From personal experience, using both, I can say that tables are far more compatible across platforms and versions of browsers and brands of browsers than css. They are simple and reliable.
css, on the other hand, allows me to control the content within cells (if I choose to use tables-- and I like them) reliably and easily.
Best of both worlds and I get far more compatibility without using hacks than if I try to use one or the other.
I really feel for the zealwith which you push .css and not tables. But really, that is such LAME zealotry. It's like looking at a toolbox and saying "hammer, you suck. I'll never use you again, and why did I ever? I'll use pliers from now on and do everything with them, not matter what."
Why can't we be *SMARTER* about it and say, tables have their place and css has its place? Make them work together, which is much easier than trying to do one or the other.
From personal experience, using both, I can say that tables are far more compatible across platforms and versions of browsers and brands of browsers than css. They are simple and reliable.
css, on the other hand, allows me to control the content within cells (if I choose to use tables-- and I like them) reliably and easily.
Best of both worlds and I get far more compatibility without using hacks than if I try to use one or the other.
IMHO