3 ms·
I'll tip my hat to the author for writing the first well-formed, non-ranting, description of why one should use Tables over CSS (that I've come across), though
by Klonoar 18y ago
I'll tip my hat to the author for writing the first well-formed, non-ranting, description of why one should use Tables over CSS (that I've come across), though I'm sure with the amount of these people that are coming out of the woodwork I'm sure I'll end up seeing more...
I still feel the need to disagree with him though. This kind of mentality is counter-productive to the web moving forward - CSS can be a bit more difficult at points, yes, but 90% of the issues that are generally encountered with it stem from IE's horrific rendering engine. We've finally gotten to a point where IE's market share is declining, and with that CSS based development will only get easier.
On one last note, CSS is being adopted in more places than just the web - for instance, there's various projects attempting to integrate CSS into the GTK setup. If CSS was really that bad and unusable, do you think it'd be getting any further adoption at all?
- jrwoodruff 18y agoJust my two cents but I would say that this argument is not counter-productive, but rather essential to the web moving forward. Until CSS is improved, tables will never go away.
- Klonoar 18y agoI guess the way I'm looking at it is that this argument has already happened. CSS doesn't necessarily need to be improved, rather the browser situation does, which is certainly not helping CSS to look better in comparison to Tables. CSS3 (and CSS 2.1, which is still not fully supported in some cases) have various properties for forcing display models, but the caveat always ends up to be IE6/7. Though to be fair, I guess you're right, this argument is rather essential to the web moving forward, I just have to wonder if this is really the argument worth having.