or more precisely, it hates intermittent network connections. The incoming changes poller for subversion (which triggered this note), the TeamCity plugin, the IDETalk plugin, and the error reporter all behave quite annoyingly in response to transient network outages. Moreover, each of them behaves differently! The only component that gets it right is the plugin manager (and how's that for irony!)
Laptop sales now exceed desktop sales. Thanks to some very sweet offerings from Apple and Lenovo, more and more development is being done on laptops, particularly in the US market. Because of this, all network activity from IDEA needs to be built to support intermittent connectivity. At very least, things that require connections need to silently and cleanly reconnect, without repeatedly asking for authentication. At best, there should be functionality to intentionally defer actions until connectivity returns, "Commit change list next time I'm connected" for instance.
Sorry if this came off as too harsh. I've just seen too many RCODs recently from the incoming changes poller and had focus stolen by the IDETalk login panel too many times. This is a small thing, but it has way too much potential to break one's sense of flow.