While we all sympathize with your stance, the author's is more reasonable.
For the client, it's really quite simple: it takes some extra hours of work to support IE6, which costs X dollars in labor. For a given site, not having IE6 support will drive away Y dollars in user revenue. If supporting it makes them more money, they should want to. If it loses money, they shouldn't.
Making this trade-off explicit with a client is good. And I think it's also reasonable to charge a premium on those hours of IE6 support, since they are extra-frustrating.
HOW frustrating it is for you will affect the premium you charge. And for you the tradeoff is more like this: am I willing to lose business with clients because they think I'm unreasonable in my IE6 support fees? Are the dollars lost made up for by happiness at work?
As long as you're thinking it through, do what you want.
For the client, it's really quite simple: it takes some extra hours of work to support IE6, which costs X dollars in labor. For a given site, not having IE6 support will drive away Y dollars in user revenue. If supporting it makes them more money, they should want to. If it loses money, they shouldn't.
Making this trade-off explicit with a client is good. And I think it's also reasonable to charge a premium on those hours of IE6 support, since they are extra-frustrating.
HOW frustrating it is for you will affect the premium you charge. And for you the tradeoff is more like this: am I willing to lose business with clients because they think I'm unreasonable in my IE6 support fees? Are the dollars lost made up for by happiness at work?
As long as you're thinking it through, do what you want.