You may want to try to build your own online service or product. You'll have accountability to customers which is obviously important but you'll also have more flexibility in your schedule.
All I'm saying is that we go to great lengths to get companies OFF the CV list. If they're on it, it's for a reason. We can't update their code for them.
We're very proactive in our compat outreach and we've had numerous conversations with sites like Google. Sites like Google are VERY aware of the CV list & the modes they're rendering in; it's not a surprise to them.
Don't assume we're doing something nefarious when it's not the case. We have nothing to gain (and a lot to lose) by breaking one of the top web properties, even if they're a competitor.
Here's a more plausible scenario. Google may have made a change to their SERPs which didn't work great in the docmode that IE11 is rendering it in. Nothing intentional, nothing nefarious on either company's part.
I think that's a more reasonable explanation than the concerns you're expressing.
If it had worked fine, it would never have been added in the first place. We don't add sites arbitrarily to the list. It's based on actual compat testing. Also every site on the list can request to be removed so if Google had tested in IE11 and discovered all was great, it's very easy for them to contact us to remove them from the list.
"For a site like Google, I see no reason why Microsoft should have put it into compatibility mode- I have to assume that Google does testing on IE and any bugs should have been addressed quickly by Google."
Unfortunately, we see otherwise during our compat testing here at Microsoft on many occasions.
Could you ask Stuart to email me a test case so I can look at it? We tried looking for a way to get a hold of him but couldn't find any short of a general email address on the company site.
Definitely more awesome code out there but I think you're seeing that from a VERY vocal minority of developers who are 1) very vested in the OSS community, 2) love to share code and 3) are pushing to get the most out of JavaScript.
As I think John eluded to, there's a number of developers that don't fall into any of these buckets and a book like this would certainly be useful to them. I was with John on the jQuery team and I know that I'll be picking up a copy of this since I'm sure I'll find some nugget of awesomeness in there that will make it worth the price.