CSS and Divs vs Tables

When it comes to building sites some people are still using tables to create their layouts.  While these still may work they are outdated and can look unprofessional.  This is where CSS and Divs come in.  Not only are they the new and latest design technique but they also can give your site a superior look.  Some other benefits to using CSS and Divs include faster load times, cross-browser compatibility, lower hosting costs, less time spent, consistency maintained, easier for SEO, etc.

2 Responses to “CSS and Divs vs Tables”

  1. The way I see it, and what I also got from reading those two articles, is that the ONLY way the table was promoted was as an easier way to do stuff that’s really really hard to do right with CSS, and might need to be rebuilt with a smaller addition. Table-style columns (equal height, background images) spring to mind. They were not promoting going back to all tables, nor going back to all tables but with CSS instead of font tags. They were promoting using table tags as a last-resort-workaround for a very limited set of setups until CSS3 gets implemented, so they can get the job done today. It may be evil evil evil to some of you, but it’s that or five more hours writing code and testing across browsers.

  2. Thanks for the comment!

    I will admit that in some situations it can save some time to just take the “easy way out” and go with a table. However, as I have become more experienced and gained more mastery over CSS I have learned how to efficiently and quickly create the elements with CSS. It may take a few more minutes, but if you ever have to go back and change, update, scale, or expand that element, it will be a lot easier if you stick with CSS and XHTML semantics with div-based structures.

    Scalability and maintainability are becoming more and more important as the web evolves and becomes more interactive. Ajax is impossible to build into poorly-formed code. If you want to save time in the long run, it’s better to do it once and do it right 🙂

Leave a Reply

Captcha * Time limit is exhausted. Please reload CAPTCHA.