For what it's worth, IDE's make java far less painful in a way an IDE could never help a dynamically typed language.
I used mostly python or other scripting languages before taking a primarily java-based job. At first I was fearful, but then I got a taste of what an IDE can do to Java.
Sure you have lots of libraries to call, and lots of mundane code to write, but the IDE is able to a) give you your options and b) autowrite the mundane code c) catch most errors before you compile thanks to tight syntax and (almost) strong typing
It can also save a lot of time over python which is prone to introduce program halting errors without any compile time notification. This is especially annoying if you have programs with a long runtime.
Same experience here. The power of Java is more apparent in larger projects where the rigid policies (ex: no multiple inheritance) and strong typing maintain a high quality standard for code and minimize those nasty deeply seated bugs.
For hackers writing short programs quickly it seems like a pain but this rigidity pays off as things scale. Great IDE implementations (eclipse) really shine when they can utilize strong typing to warn of syntax, compile-time (and some logical) code faults while coding. In my experience catching these problems in the IDE yields a greater time savings in the long run (vs interpreted languages)..
I used mostly python or other scripting languages before taking a primarily java-based job. At first I was fearful, but then I got a taste of what an IDE can do to Java.
Sure you have lots of libraries to call, and lots of mundane code to write, but the IDE is able to a) give you your options and b) autowrite the mundane code c) catch most errors before you compile thanks to tight syntax and (almost) strong typing
It can also save a lot of time over python which is prone to introduce program halting errors without any compile time notification. This is especially annoying if you have programs with a long runtime.
In the end, its just another tool in the bag.