Improve Documentation around Using Socket.IO with multiple nodes

I would like to see the documentation expanded around the following:

It makes it sound like there being no fallback to polling is such a horrible thing, however I don't see a lot of concrete examples of what that means. Based on additional research, it seems to mean the following:

• won't support IE < 10

What else am i missing / what implications are there in terms of this? It also hints that if you don't care about polling you should use another library instead, but I don't feel like that's a solid reason, especially if you're already familiar with socket.io and how the middleware and connection authentication works.

There is also an additional part of the documentation that mentions "living dangerously" if you only use websocket transport, but again I don't feel like it explains why?

it mentions a socket connection failing due to a few reasons, however, what are other implications if any of this? What's wrong with requiring people to connect through the websocket protocol? How common is it (or at least give a more concrete example of a use case) that if you don't allow polling as a transport option a certain subset of people won't be able to use your app?

I'm opening this issue to have this discussion, learn the answer to my question, and then am 100% willing to update the documentation to provide more concrete examples of the points in question if that's acceptable.

Thanks!