In case you need to worry about this sort of thing: here's the MSDN doc that breaks down the differences between "real IE10" (on Windows 8) vs. the Windows 7-compatible IE10 "Release Preview".
tl;dr: Unless you're dealing with touch events, and some of the -ms-vendor-prefixed stuff, you're probably fine.
Nice write-up by Todd Kloots at the Twitter Engineering blog about their
pushStateimplementation, and some of the pitfalls to watch out for when mucking around in those APIs on your own time.
Scott Hanselman (back in 2011) dinging &yet; over their "&!" product, and how they handled browsers that don't handle WebSockets. For the most part, Hanselman's headline is right on but…
…commenter David Carson more/less summarized my true feelings on the matter.
The web has become a powerful platform for delivering high quality software, but front-end developers everywhere recognize that it's not a level playing field. Yes, there are shims and fallbacks and polyfills. Yes, there are ways of progressively enhancing your offering. But there's also a point where you should be able to say: "This is high-quality software, and these are the requirements."
Sometimes you need to make that choice. And in &yet;'s case, and especially in the case of &! — I think that they totally made the right choice. They chose the features they wanted to deliver and focused on those. (And I'm pretty sure it was just a prototype at the time Hanselman wrote this blog post.)
Emma Marris, writing for Slate:
“It feels more responsible and ecologically sound to eat an animal that was raised wild and natural in my local habitat than to eat a cow that was fattened up on grain or even hay, which is inevitably harvested with fuel-hungry machines,” writes Christie Aschwanden, a self-described “tree-hugging former vegetarian.”
[All] it takes is overturning two long-held beliefs among many urban liberals: that it is wrong to personally kill animals and that hunters are all rural conservatives.