You still can put a big red sign with "This browser is not supported, here's why.", and let the user decide if they want to try it with IE just to see if is worth it the browser change.
IE9 is actually not that bad, and IE 10 should hopefully be very good. As a developer my bigger problem with IE9 is that sometimes I forget to comment a console.log after testing.
Their problem is that they want to be "pixel-perfect" across all browser.
I get why, but as a User I don't really care as long as everything else works. And chance are that with IE9 and IE10 it will.
I'm not a IE user, but when we stop supporting IE6 we put a big sign saying that if there were problems we won't fix them and to download a modern browser. But people still went to the site even if some divs were in crazy places because basic function they needed worked and maybe they hadn't the chance of upgrading their browser.
If one of your client is once on another computer with only IE installed and doesn't have permission to install another browser, the fact that he can't use the website at all, is that a feature ?
You can use the javascript shim for console in HTML5 boilerplate to make it safe for use in IE. It even logs output to a global array, so you can inspect the console output in IE.
The only thing IE10 seems to lack that's really significant seems to be WebGL. Which means IE9 may be the last version of IE that will ever "hold back" the web.
