[UPHPU] More CSS frustration

[Wade Preston Shearer]

> This gets at the core of where I think we disagree: because cross- 
> browser rendering is more robust with technologies that aren't new  
> and poorly supported, I can rework it faster if I don't have to  
> mess around for hours on end with hacks trying to make my divs  
> float the way I want without using Javascript to dynamically resize  
> them when the page loads.

This isn't because the technology is lacking. This is only because  
your experience and knowledge of the new technology is not as robust  
as your experience and knowledge of the old technology.


> Point 2: I very very very rarely have a client want to majorly  
> rework the design of the site without wanting enough other changes  
> that the markup would need to change anyway. CSS Zen Garden is by  
> far (by _really_ far) the exception, not the rule. The only places  
> I know of where changing the whole look of the site happens often  
> is in sites that support skins or themes, but they're always  
> displaying the same data, no matter what theme you're using.
>
> When you're working for a company, they don't change their  
> corporate branding very often.

I completely disagree. I have heard you use this as a table-based  
defense many times, but it still surprises me; especially with all of  
the clients that you have. I have re-skinned sites many, many times.  
I have moves columns from the left to the right and move blocks up  
and down, many, many times… things that could never had been down  
with solid separation.


> 1) Easy to maintain - When maintenance work is necessary, I can do  
> it just as quickly in my way as you can in yours I'd bet. So me  
> switching would be a disadvantage, cause I'm not familiar with all  
> the CSS quirks, but I am familiar with most of the quirks that  
> affect the way I do things.

I disagree. I believe that the benefit afterwards would be worth the  
educational/training investment.


> 4) Easily ported to different output formats - This one is a lot  
> like number 2 above: Do you know how many times we've had a client  
> ask for us to make the same web page/site available in html/css as  
> well as xml, wml, or any other different output format? I'll give  
> you a hint: I can count them on zero hands. If they assign 0 value  
> to it, it is a worthless advantage for them/me.

Even if the client isn't asking for it, why not building with the  
ability to do so if it's just as easy if not easier?