decloak logo
Cart cart | sign out  
css versus tables
 css vs tables: round I. 
    1. benefits to css
 
    2. is full css faster
 
    3. Return on
Investment
 
 
    4. Long Run
Maintenance
 
 
    5. w3c standards
are useless
 
 
    6. structure
and content
 
 
 
 css vs tables round II. 
    7. point:
        tables are for
       tabular data...

     counter point:
       yes, but tables
       make up
       databases.
       Duhhh!!!








    8. Hey Stupid
 
    9. Bandwidth Savings
 
    10. accessibility and
     $4000 wheelchair
     ramps
 
 
 
    11. Spend Time
Learning
 
 
    12. Captured
CSS Flagship
 
 
    13. Selling your
product
 
 
    14. May work well
 
    15. Standards
Merry Go Round
 
 
    16. Extremists
Update
 
 
 
 
  
   
 
    Separation of Structure and Content via CSS
    makes things more organized.
  1. ORGANIZED or SCATTERED? Just how does this make a web page more organized? And, does this so-called organization really save time and money? When you have this piece of the web page here, and that piece there, and that other piece way over there for "modularity", you still have to eventually put it all back together in your head to understand what's going on in the first place. And that's going to take a lot longer in billable hours as the code is now scattered all over the place. It removes many of the benefits of wysiwyg as it now becomes a scavenger hunt!

    One should ask these, "purists and elitist" CSS people who advocate FULL CSS, "At what point is abstraction too much?"

    If I have to make a change in the CSS page for a style, that's one thing. But to switch back and forth to change the position of a table when I could use the WYSIWYG design tools, that's a waste of time.

    Each section of the page almost always stays in the same position, the footer is at the bottom, the header is at the top, and the content is somewhere in the middle. Just exactly what advantage do I have when I separate all this information into the CSS file? Certainly not time as one would have to bill the client more hours. (And if it's done in XHTML to describe the content, a <td> tag can, just as well, have an ID attribute that will serve the same purpose as an XML identifier.)

    All this separation (layers) sounds a lot like the layers of government bureaucracy doesn't it? Each service/layer trying to justify their existence with complete nonsense and then they tell you need to go to a different department or government level to do what you want to do. It's called the "run-around".

    And that's what you will be doing with this so called "more modularity" of
    CSS-P. You will be RUNNING AROUND in circles just like in government.



flush lines that auto stretch vertically and horizontally
 
terms of use | privacy policy
copyright © 2003 - decloak, inc. all rights reserved