In his opinion, Java the programming language was on its way out whereas Java the runtime environment was here to stay.
Absolutely. Java the language is a chore, leading to very verbose code. The JVM however is one of the best things since sliced bread. A managed environment like that is extremely useful.
If you find that you resemble that description, then check out Clojure which is a version of lisp that compiles to Java byte code running in the JVM. It can, but doesn't have to, be pre-compiled and it is dynamically typed. You can provide type hints but you don't have to. For this reason, Clojure programs are much more dense than Java programs. Less typing in order to get the job done.
Another good option is Groovy, which very easy to get into for Java programmers, since 99% of legal Java syntax is also legal Groovy syntax. But for everything, there's also a better, more readable way to do it. Best interaction with Java of any JVM language. It's basically what Java should have been.
Be careful what you ask for. All that typing means that you can find and fix a lot of bugs in the compile step. With dynamically typed languages, you get to find those bugs at runtime. Maybe that is why other posters here believe that Java is for the B programmers.
No, if you're a competent programmer, you don't rely on the compiler to find all your bugs, because it won't. You rely on unit tests, which means your basic bugs will be found at build time. The percentage of bugs that a statically typed compiler will find for you is small. You still need extra tests to find all your other bugs, and those tests will also find your basic type errors.