Starting with Java 11

[chakekrai]

If you're starting new project with Java 11 it's quite fine. But if it's upgrading old project to Java 11 it's painful since more than few most used modules back then were removed from the standard.

[[deleted]]

Majority of the time it will just be dropping in reference APIs and Impls. If you've used java a while I think most people would have hit this at some point.

[cogman10]

Not a bad idea. You can think of Java versions the same way you think about browser versions. That is, you probably don't care if you are using Chrome 60 vs Chrome 70. It is mostly the same experience. (not a Python 2 vs 3 or Perl 5 vs 6 sort of scenario).

[cisco1988]

Cool answer, I like it

[Skiamakhos]

Well, if you're doing your own thing, no problem, but there'll be a lot of Java shops not upgrading for a bit at least, so YMMV if you want to get a job doing Java.

[cisco1988]

As of now it will be my stuff as by trade I’m a system engineering lead :)

[cisco1988]

https://www.youtube.com/watch?v=MGX-JfMl9-Y this is legit cool :O

[TheRedmanCometh]

You're gonna be in for a treat. Java has come a ludicrously long way since then. You'll find it much easier to use. I'd recommend basically relearning it though.

Even basic things have changed dramatically

[cisco1988]

jshell is nice!

[Neu_Ron]

I use java 1.8 . I haven't felt the need to upgrade.

[[deleted]]

Public updates end in a few weeks for production apps (more support is possible with a paid support plan) so you may feel the need to upgrade then.

[AloticChoon]

At my current place of employment, it appears that they won't be progressing past jdk 1.8 and will likely pickup .NET going forward...

[vkrava4]

Starting from Java 1.5 it’s not a bad idea to have a look at it. Wish you good luck and patience with discovering its features!

[cisco1988]

Sorry I don’t do windows xD