Well, respectfully, you sound like a lot of people I know that never really learned their way around Java, therefore, it must suck.
If you're working on something where static typing and the compilation step are non-starters, then yeah, don't use Java or C++.
Regarding the libraries -- Java collections? java.util.concurrent? Guava? Those 3 by themselves will get you a long way, and for anything more specific you usually have a choice of several libraries.
I spent many years of my life writing Java. I don't mind static typing and compilation; I use Haskell extensively. (The difference being that Haskell's static typing actually makes correctness guarantees, and that when developing you can test your code in the REPL.)
I tend to think of libraries as "make me a nice HTML form" or "talk to this strange router" or "connect to Twitter". Every language has collections, concurrency, and various utility libraries like Guava. Nothing wrong with the examples you list; I've used them and am not that impressed.
If you're working on something where static typing and the compilation step are non-starters, then yeah, don't use Java or C++.
Regarding the libraries -- Java collections? java.util.concurrent? Guava? Those 3 by themselves will get you a long way, and for anything more specific you usually have a choice of several libraries.