This usually solves for weird, deprecations, and routes around profoundly unfriendly browser barriers, which, sadly and admittedly are required from a security standpoint for most clueless users.
I prefer using Eclipse over IntelliJ CE, because Eclipse settings for static libraries that aren't handled by source control are a bit more concrete. IntelliJ CE is well-suited for many professional coding activities, but buries some commonly used, yet clunky settings that are right on the surface with Eclipse. Namely JRE/JDK choices, and build path settings for static jar files.
On the other hand, you might need to know a bit about Java, to do this. For most HN users, and even many gamers, this is generally not too much of a problem.
