If you learn Java you will be able to get a job doing it. So in that sense it is relevant. I personally feel it is a dead end though. And this is coming from someone who loved Java when he first played with it 15 years ago (previous experience was C++ / VB6 / BBC Basic though!)
If you want to enjoy your job, or your hobby, choose a better language.
I'd suggest Clojure or Haskell. But where I live at least it is a fight to get to do paid work in those languages, but a fight that is worth it.
Hard to explain why Haskell is better than Java in a little comment. I say learn some Haskell and Java and discover for yourself what you prefer.
I have been looking around for jobs here in Spain, a lot of the better paid senior level stuff is for either MS stack, or Java (they all seem pretty corporate style). There are Python jobs around, but more mid level.
Same problem here. It takes some ingenuity to get paid well and use the stack you love. I am working on it. One way is to convince your current company to try something new on a small project to get its feet wet.
Any MS shop could consider F# and Java shop could consider Scala/Clojure as in each case it compiles down to compatible ones and zeros.
Or it could be a case of get a .NET/Java job at an open-minded enough company.
One of my arguments to introduce F# (when I am ready to) is that F# is now (a probably better version of) what C# is going to be in 5-10 years time, so lets get ahead of the curve.
If you want to enjoy your job, or your hobby, choose a better language.
I'd suggest Clojure or Haskell. But where I live at least it is a fight to get to do paid work in those languages, but a fight that is worth it.
Hard to explain why Haskell is better than Java in a little comment. I say learn some Haskell and Java and discover for yourself what you prefer.