TR Forums

While people who use Java for heavy development have probably already been messing with the beta versions of the software heavily, Oracle finally released the JRE & JDK packages for Java 9 to the world at large today: https://fossbytes.com/java-9-features-r ... ad-course/

Incidentally, I downloaded the official JRE packages for my Arch system not because I love Java (quite the opposite) but because I'm forced to use Java Web Start to run an important but relatively simple application at work. And...... the application broke when I tried to run it with JRE 9. So I rolled back to version 8. Yay regression testing. Incidentally, I have zero control over the broken application so I can't go fix it or even really debug what the problem is.

chuckula wrote:

And...... the application broke when I tried to run it with JRE 9. So I rolled back to version 8. Yay regression testing. Incidentally, I have zero control over the broken application so I can't go fix it or even really debug what the problem is.

Ahh, good times.

Oof, this is gonna suck.

chuckula wrote:

Incidentally, I downloaded the official JRE packages for my Arch system not because I love Java (quite the opposite) but because I'm forced to use Java Web Start to run an important but relatively simple application at work. And...... the application broke when I tried to run it with JRE 9. So I rolled back to version 8. Yay regression testing. Incidentally, I have zero control over the broken application so I can't go fix it or even really debug what the problem is.

Be honest, though - you completely expected that

TwistedKestrel wrote:

chuckula wrote:

Incidentally, I downloaded the official JRE packages for my Arch system not because I love Java (quite the opposite) but because I'm forced to use Java Web Start to run an important but relatively simple application at work. And...... the application broke when I tried to run it with JRE 9. So I rolled back to version 8. Yay regression testing. Incidentally, I have zero control over the broken application so I can't go fix it or even really debug what the problem is.

Be honest, though - you completely expected that

You have a point that I never said I was surprised by the result

Yeah, this is gonna suck. Although I don't develop in Java myself, we have massive amounts of Java code here where I work. There's already some internal chatter about how it may eventually impact us.

just brew it! wrote:

Yeah, this is gonna suck. Although I don't develop in Java myself, we have massive amounts of Java code here where I work. There's already some internal chatter about how it may eventually impact us.

With a lot of installed code bases it's not so much of question of wanting some whiz-bang Java 9 feature that makes you want to upgrade. Instead, it's the dread of realizing that whatever older version of Java you are using won't be supported forever and you'll have to upgrade at some point. That's especially true if the upgrade is forced due to some unpatched security bug in an old version of Java.

I had a use for Java once...hmm.

Probably not worth it, considering it's just another thing needing regular attention.

Well you've still got six months of updates for Java 8 at least. The release notes have a boatload of changes and I'm sure this is going to break a bunch of code. Good luck, guys!

Here's one spot where working in a Microsoft shop isn't so bad.

It's almost like they're trying to break Java compatibility these days. Hurray for legacy software that won't ever get updated...and maintaining (and securing) old-as-dirt packages to keep things running in production.

Oh, I guess my one thing already ended development anyway

MileageMayVary wrote:

chuckula wrote:

And...... the application broke when I tried to run it with JRE 9. So I rolled back to version 8. Yay regression testing. Incidentally, I have zero control over the broken application so I can't go fix it or even really debug what the problem is.

Ahh, good times.

Could be worse! Could be the Cisco ASDM. I've resorted to a Mint image running from VirtualBox on my Windows desktop just to open that.

I think it's (past) time to have a serious look at virtual desktops for legacy Java apps, especially ones running in the browser. I still have several of those (fortunately on not many computers) and they invariably require Internet Explorer and an ancient unsupported JRE with multiple security holes.

Finally. We use Java for all development, other than one JNI library written in C++. Optional.stream() will be very helpful with both flatMap() and findAny() in streams. Modules are too new to play with yet, though I see the utility. We'll see how long all of our favorite Maven projects take to get modularized. Reactive streams will hopefully speed the adoption of libraries like RxJava. And, for all the other Java annoyances, we use Project Lombok to make boilerplate less painful.

derFunkenstein wrote:

Well you've still got six months of updates for Java 8 at least. The release notes have a boatload of changes and I'm sure this is going to break a bunch of code. Good luck, guys!

Here's one spot where working in a Microsoft shop isn't so bad.

No, instead you have to deal with the prospect of your ENTIRE codebase being deprecated! I don't understand the issues people have with Java compatibility. It's usually due to crufty coding practices and crufty programmers are always gonna do what they do. My codebase runs on Java 6 onwards with no issues on any version of Windows, Mac OS or Linux... Or any web browser from IE6 onwards including Chrome, Firefox and Edge...