What world do you live in that non-OSS software is bug-free?
Sorry, you don't seem to have actually read what I wrote before posting your reply. Here is the relevant part again:
"Just as important, the relatively few serious bugs in the more recent versions of IE tend to be well-known, and the necessary workarounds are well-established and stable because the goalposts don't move every six weeks."
I don't see how that equates to anything like what you wrote.
On with your next point:
What, besides your own prejudice, justifies supporting a browser that you admit has some serious bugs, and also does not properly implement the web standards?
And again with the twisting of words. Here to remind you is what I actually wrote:
"While [recent versions of IE] don't have all the bleeding edge shiny, the basic functionality does generally work very reliably, and actually IE9+ have a lot of the more useful recent developments anyway. Just as important, the relatively few serious bugs in the more recent versions of IE tend to be well-known...
I put the parts you twisted in bold for you so you can see where you went wrong.
In any case, I fail to see how making decisions based on extensive practical evidence constitutes prejudice. Prejudice would be, for example, saying I was going to advocate a browser that consistently shows up more bugs in basic functionality than all the other major ones instead of IE, just because the more buggy browser is not written by Microsoft.
And there is a difference between having a feature and supporting standards. I think if you're going to claim to support a standard, the feature should actually work. Chrome has had, and in many cases continues to have, obvious and fully reported bugs in CSS rendering. These include popular CSS3 effects like gradients and rounded corners not drawing properly under various conditions. They also include basic CSS 2.1 text styling problems like the infamous letter-spacing limitations, because Chrome still relies on its own very poor text rendering rather than using the far superior tools built into various host operating systems. It's not as if these kinds of issues are big secrets; some have been in the bug tracker for years with numerous people echoing the problem.
I don't see any facts or evidence in your post -- that would presumably detract from your trolling.
I was posting in support of TFA, not trying to make an independent case of my own.
However, I have made my own case based on my own evidence on several previous occasions on this forum and elsewhere. Unfortunately, even if you cite a bunch of specific issues, the response is rarely any better than your own: someone in denial of the situation who thinks anyone criticising their beloved browser must be trolling and can't possibly have actually experienced numerous documented and repeatable bugs, even though the bug tracker is a matter of public record and mere seconds searching it would confirm the kinds of bugs people are citing.
Charge for compatibility beyond IE, and charge for any time spent submitting bug reports.
Sorry, but I'm a professional, and as such I do the job my clients hired me for. If Google would like to hire me to help test their code, I'll be happy to quote them a suitable fee like anyone else. But right now, my real, paying clients typically hire me to produce web apps that work for contractually specified targets, not to provide subsidised debugging for someone else's product.
Today, those specified targets are usually something like IE8, IE9 and IE10, because with the deliberate policy by both Google and Mozilla to avoid stable versions and push updates every few weeks, it's difficult to specify support for Chrome or Firefox in any useful way in a contract even if you do want to. Without a stable platform to test against, there is no way to write acceptance criteria that are going to be relevant for more than one release cycle of those browsers, which for many projects isn't even time to run through the QA/release process fully.