Hm…it seems like `<noscript>` is a different beast in IE8. For example, trying to set its innerHTML just causes an error. This will is a problem: if you write a component that uses `<noscript>` (in order to leverage server side rendering), it will error when React tries to mount it.

I'm not exactly sure how best to get around this. I supposed we could sidestep the issue by telling it not to render any contents when mounting into the DOM, but I'm not sure how best to recognize that. Thoughts?