[valuegram]

>> anything prior to the release of their favourite framework, didn't really exist, and if they do acknowledge its existence, it's only to observe how worthless it is. It's almost religious in nature.

For me at least, its not about religion but economics. Writing standards compliant code that works in all modern browsers costs a certain amount. Writing standard compliant code that is also backwards compatible with older technologies and legacy browsers may cost significantly more. The cost is one issue, of course the larger program is the value. Legacy browsers like IE6&7 compose slightly over 3% of the market share last month. Without even getting into the demographics of those people, it often isn't worth it to tweak for those specific cases.

That being said, I always leave it up to the customer. This is the issue in the browsers, here is your traffic effected, this is what it would cost to fix.

I can see the agitation with IE6&7, but the newer releases have gotten much better. For the most part, something I develop mainly in FireFox works fine in the newer IE releases.