Forum Moderators: not2easy
Anyways, I'm trying to determine if I should just re-create everything with tables or continue to work with their css - or re-create it with my own css. I just wanted to see if anyone could provide a real good reason for using css-div layouts rather than tables. Or - more specifically - css div's ONLY vs a hybrid site. I'm by no means against using css - I use it all the time WITH tables to provide the skeleton. I see CSS as an add-on to html, not a replacement for it.
Before they are brought up I want to address several of the most common arguments I've seen. First off - speed! There is no REAL speed benefit of using css over tables. The difference is in the milliseconds - not something I need to worry about.
Second off - bandwidth cost! While css might be cheaper with a host that you pay so much for every x amount of MBs transfered - all of the hosts that I've used give you x amount of transfer each month. I've never seen any of my websites approach this limit and so it is not a real concern.
Thirdly - maintainability! I personally find it much harder to change the design of a css layout - especially a large one - over a table/hybrid layout. This is especially true when I take over someone ELSES css code. It takes a long time to familiarize yourself with how they coded the site! You constantly have to switch between the css file and the source file to see what the heck is going on!
Fourth - division between the design and the content! This is a non-issue for me. By using php, jsp, or some other server-side language I can separate the design from the layout and use the server code to piece together the pages for me. I can do website wide redesigns without ever touching the files with the content, and I can do them in a split second!
Fifth - its the standard! CSS is not a true standard. If it were - you wouldn't have to hack or make multiple files to support all of the main browsers. Tables have css plain beat on this point - everyone supports tables and they render the same. Also, I've never been particularly interested with keeping a web standard - I'm interested in what works! It's a nice idea but its not there yet.
Sixth - tables are archaic! Many people like to treat tables like they are some ancient technology that has been replaced by something that is all around better. This is a lie! Tables maybe old but thats what makes them so useful! EVERYONE supports them. That's a true standard right there. And when combined with CSS they can create designs which tables alone can't create and designs that CSS-div only designs can't create - or at least designs that would take far to long to do with CSS only.
Seventh - tables were made for tabular data! So what? Many things start out with a single idea in mind, but they are adapted for other - potentially better - uses. This is a stupid self-righteous argument that has no real backing.
Eighth - philosophical/ethical issues! These range from making your site the "right way" because its "professional" to making your site more accessible to blind ppl. These too are silly self-righteous arguments that have no real backing.
I think that covers just about all of the common arguments I've heard. So, if you have any real reason to use CSS over tables/hybrids please share!
Like one guy said on there - tables are good to provide the structure and css is good to fill it in (paraphrasing). Good old hybrids :D.
Were on the 2nd page!
