On Oct 24, 2006, at 5:58 PM, Css Discuss wrote:

> What do YOU (plural) do?
>
> Do you say, "I'm sticking ot standards, piss on your browser if it  
> doesn't
> look good!"?

Nope.

> Do you make your pages simple so that there's flexability in the  
> design, so
> that browsers don't notice the difference?
> (Think Google)

Almost got it, but that's also a bit extreme.

> Do you go bonkers (or spend a ton of time) learning the work  
> arounds so that
> instead of a specialist in CSS you become a specialist in the work  
> arounds
> that hopefully will be gone in a few years?!?!

Exaggerated, but yes. Exaggerated, because it doesn't take tons of  
time. Rachel Andrew, bless her heart, has pulled together a bunch of  
them in CSS Anthology (Sitepoint) and Joe Lowery's CSS Hacks and  
Filters is another good source. Websites like http://tantek.com/ and  
http://www.positioniseverything.net/ as well as css-d's own http:// 
css-discuss.incutio.com/?page=CssHack will give you most of what you  
need. You can spend a few free hours gaining a general familiarity  
with the concepts, to help you find the required hack/filter faster  
when you need it, or you can wait until you're up against it and then  
look for it.

They key word in your "gone in a few years" comment is "hopefully."  
Most of the particular bugs will be gone in a few years, though some  
will, I'm sure, still be with us. The background-position: fixed bug  
of IE5 was still there in 5.5, and in 6, and it may quite possibly  
still be there in 7 (I haven't looked for it there, yet). So it  
stayed around for a decade, give or take.

But even if the particular bug that a workaround was designed for is  
fixed, it'll be several more years after that before you can safely  
stop working around it, because your audience will continue to use  
buggy browsers. Those of us who survived Netscape 4.0 can tell you it  
quite often seems users are most attached to the browsers that  
perform the worst. And besides that, you can often use the workaround  
to make something else work as well.

So you're not spending time learning techniques you'll only use for a  
few months or a year. The general idea behind the hacks and filters  
will be useful for many years to come. There's a lot to be said for  
Budd's POV, you should never get so you rely on only one tool, but  
they remain useful tools in your toolbox and it would be foolish to  
refrain from using them entirely.

> I'd really like to get good with CSS, even REALLY good, I totally  
> intrigued
> by them, as much as programming.
> It just feels hiking in deep mud,.. WAY too much work. I need to  
> earn a
> living here.

Get familiar with a concept Covey calls "Sharpen the Saw." You need  
to do things today that won't pay off until later, things which will  
keep your skills sharp and keep you from becoming obsolete. This is  
one of those things. No, you won't get paid for it today, but without  
it you may not get paid tomorrow. You can't keep cutting wood  
efficiently if you don't keep the saw sharp.

Hey, if it was easy, *anyone* could do it. And *then* how would you  
get paid for it?

Have Fun,
Arlen

------------------------------
In God we trust, all others must supply data

______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7 information -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Reply via email to