Oh, and you have to use this garden spade...
Oh, and the handle is made out of jelly...
Oh, and the ditch is on the beach so the tide will be coming in any time now.
Hyperbole, yes. Web development isn't exactly ditch digging, but if you really want to understand why so many web developers are openly hostile toward supporting these older browsers, it's because the exercise is tantamount to digging ditches with jelly-handled garden spades on a rigid time table. When you get in to these much, much older browsers, it's a back and forth game of break/fix whack-a-mole. It's broken in one browser, so you try to fix it by using another approach, only to find that it's now broken in the current browser. That or you end up using ugly work arounds that just cruft up the application and make maintenance a nightmare.
Ultimately this comes down to a business decision. I consider each browser version as a market to be sold in to. I may find it an unrealistic business proposition to increase my developer hours by 30%, just to support a specific browser, when there's a big fat market of current browser users ready to use my application.
But, if you* really don't enjoy what you're doing, do something else. There are always going to be browser differences and they're not all IE-related. But you're getting paid to know those differences and handle them so your customer gets a good experience.
* Again, "you" == the wider population of Web developers.
It's a matter of trade-offs that have to be made based on intended audience and information available. No need to be offended.
In any event, the cost argument is the purview of the business owner perspective, not the Web developer. And it's hard to look at in isolation. I don't know that many sites that wouldn't love to have another 5% of traffic. Yeah, it may cost more to support older browsers, but driving traffic to a site costs money, whether through ads or spending time on inbound marketing. Trying to bump conversion rates on your existing traffic costs money and time as well.
There's obviously a balance to it. At the extreme end, I know of businesses that support anything with > 0.5% market share because at the volume they operate at, it's worth millions. At the other end, I see startups fight tooth-and-nail working on their funnels, while throwing away legitimate sources of revenue.
Anyway, it seems like we both agree that it should be a deliberate decision.
Strangely enough, we didn't lose customers. It turns out that people were using NS4.x because we supported NS4.x. They will upgrade if they have a reason to do so.
If you've written the site/app well, it will work in Lynx, fer cryin' down the sink. It won't be pretty or slick, but it'll work. There is absolutely no need to make a site feature-for-feature identical or pixel-perfect across all browsers, as long as the functionality is there. And if users understand that their browser is holding back the experience, they will change the browser.
There are just a lot of vocal web designers on the web, go figure.
We all have to do things we don't like in our jobs, that's just part of it being a job. I can even accept a certain amount of healthy advocacy. Encourage people to upgrade if you'd like. But outright refusal to do your best because your customer doesn't run the browser you wish they did is just a very odd tactic to take.