Oracle Announces Java SE 9 and Java EE 8 (oracle.com) 64
rastos1 writes: Oracle has announced the general availability of Java SE 9 (JDK 9), Java Platform Enterprise Edition 8 (Java EE 8) and the Java EE 8 Software Development Kit (SDK). JDK 9 is a production-ready implementation of the Java SE 9 Platform Specification, which was recently approved together with Java EE 8 in the Java Community Process (JCP). Java SE 9 provides more than 150 new features, including a new module system and improvements that bring more scalability, improved security, better performance management and easier development to the world's most popular programming platform.
Maybe most popular... (Score:4, Insightful)
...but the way Oracle runs it, probably getting to be most-hated and most-abandoned too. At some point most-abandoned will cross with most popular and it won't be most popular anymore.
Re: (Score:3, Interesting)
Well, I think Oracle is doing right in regard to Java. Even better than Sun did in the years prior to its acquisition. I know it's cool to criticize Oracle no matter what they do but... facts, please.
Re:Maybe most popular... (Score:5, Insightful)
When faced to make an "Enterprise Level Product" and you have to pick a Language to code it in, you have few choices that will get past the execs. .NET, Java, C/C++ The other languages out there from Node.JS, Python, Ruby, PHP, Rust... Either do not have "Enterprise Support" (whatever that means) and in general these lanagues the Execs never heard of them before and really don't want a lecture to explain it to them.
You have
Then these big name languages have fancy IDE interlaces that can make frameworks from UML graphics and a bunch of crazy expensive addons that allow the sales men who such executives trust more then their own staff .
So with all this You have .NET which is Java only for Windows. Then you have C/C++ which often will take a lot more effort to build, and there is a heck of a lot of testing needed for every new platform.
So Java unfortunately is still a good choice with the restrictions of the corporate environment.
Re: (Score:2)
Yeah but the buzzwords of ROR, Node.js, and Rust are CIO compliant.
Re: (Score:2)
Except they may be too new for them to use. We have the Execs who were Web Designers during the 1990's Dot Com boom. Who had learned the new software is often stuff that is the most unreliable. Granted many of the newer languages have more safeguards but they don't know that.
Re:Maybe most popular... (Score:5, Insightful)
When you're taliking about Java, you're talking about financial institutions and other really large corporations. They build applications they intend to use for decades. That's where Java is king, and it has 20 years worth of toolkits for that purpose. This isn't a realm where people give a shit about the latest sexy language, and where security and reliability requirements are a helluva lot more stringent than, say, Facebook's.
Re: (Score:2)
You call up the company, that you are paying thousands of dollars a month, and put it on the possible wishlist for the next version which you will need to pay for the future upgrade.
Or you open a ticket and the vendor sends you a link to the stackoverlow site. (i Had that happen before too)
Re:Maybe most popular... (Score:4, Informative)
Re: (Score:3)
So they caught mono?
Re: (Score:2)
Re: (Score:2)
I agree. Why should Oracle (or Sun, previously) be on the hook for providing security updates to five year old versions of Java? That is a logistical nightmare - multiple branches, multiple test configurations for each, and a ton of time and effort. Java updates very rarely break backwards compatibility anymore, so users should update.
Re: (Score:2)
I just installed it
on a related note I have to punch myself in the balls just to get it up
Re: (Score:3)
Re: minus project valhalla :( (Score:1)
No project ever needed any of that. Every single piece of software could be written in assembler, so no your project does not 'need' this.
All 9 of us are thrilled (Score:4, Insightful)
I will let them know.
The rest of us are stuck with Java 1.4.2, 6, and 7 due to poorly written apps using RMI to go to c:\program files(x85)\...to check version numbers and using == instead of = to run.
Or we left long ago to Ror.
Re:All 9 of us are thrilled (Score:5, Insightful)
You will never escape poorly written software no matter what language it is. One of the toughest things to teach new coders out of school, is to think forward.
These are most common arguments with New Hires.
1. Don't hard code paths in the system. Especially if it is in code that needs to be compiled.
2. Don't try to be too clever with condense code, There will be a requirement change and less clever code is easier to fix.
3. Don't drop your custom library files into the compilers library folder. This will make migrating the software to an other platform more difficult.
4. Avoid 3rd party tools and add-ons as much as possible. As they may no longer be supported in the future or work in newer products.
5. Make sure you use code that works well on most Systems, avoid using OS particular features unless absolutely necessary. The OS Maker may choose to change or drop that feature in the next version, or we may want to change OS's in the future.
Re: (Score:2)
You may make people happier, but you will more or less live your life doing a humdrum job.
For the most part with these newly hired coders, once they realize why we do things the way we do, and after an update and they find their mistake that they did in protest of the old guy who seems to be stuck in his ways, actually went to bite them in the butt. Will learn their lessons, and actually be much better coders. However the problem is a lot of organizations don't keep the developers long enough to learn the
Re: (Score:2)
You may make people happier, but you will more or less live your life doing a humdrum job.
For the most part with these newly hired coders, once they realize why we do things the way we do, and after an update and they find their mistake that they did in protest of the old guy who seems to be stuck in his ways, actually went to bite them in the butt. Will learn their lessons, and actually be much better coders. However the problem is a lot of organizations don't keep the developers long enough to learn their lessors, and keep on dumping inexperienced code to the the next inexperienced developer compounding the problem.
And with a nice developer job you can buy lots of Pizza and Tacos too. Wahoo win win!
Re: (Score:2)
But but ... but they saved $5,000 by going offshore with that Java app!
Meanwhile got hit by wannacry because they were forced to use an insecure version of Java in the process and spent $250,000 on a security consultant to fix it. But they saved $5,000 by offshoring.
Re: (Score:2)
I will let them know.
The rest of us are stuck with Java 1.4.2, 6, and 7 due to poorly written apps using RMI to go to c:\program files(x85)\...to check version numbers and using == instead of = to run.
Or we left long ago to Ror.
What sort of cavern do you call "work"? Being on Java 7 is not bad, not even 6 if we are pragmatic. But what you are describing is just insane. Obviously, everything I'll say is annecdotal, but I've not seen such crap in a long time. Who does Windows-dev specific work with Java?????
Re: (Score:2)
I will let them know.
The rest of us are stuck with Java 1.4.2, 6, and 7 due to poorly written apps using RMI to go to c:\program files(x85)\...to check version numbers and using == instead of = to run.
Or we left long ago to Ror.
What sort of cavern do you call "work"? Being on Java 7 is not bad, not even 6 if we are pragmatic. But what you are describing is just insane. Obviously, everything I'll say is annecdotal, but I've not seen such crap in a long time. Who does Windows-dev specific work with Java?????
Dude I got back in I.T. doing desktop support. Every company uses ancient Java with terrible security. We can't patch it as all the code does an == and not a less than or equal (slashcode cut off my previous comment) so if a version number is too high it will throw an exception.
One company uses Java 1.4.2. Not 1.4.1 or 1.4.3, but 1.4.2 due to this doing RMI to c:\program files (x86) and checking the path to see the JRE version instead of damn calling the method to do this! Here is the funny part which is wo
Re: (Score:2)
Looks like gross incompetence to me. And so gross incompetent use of Java turned you into a hater of Java, makes perfect sense. I guess you must hate all programming languages then, as I've seen gross incompetence in most of them. How you can even bear to use Windows is beyond me.
Anyway, I'd decompile the software involved, change that "==" into a ">=" (or remove the check altogether) and be on my merry way.
Re: (Score:2)
You know, this is actually your own fault as most companies do upgrade. You should have the balls to pack up and leave and work at a company that is with the times (if that is Java 8 or 9 or another language, it doesn't matter). You are limiting your potential and future value by continuing to work with older software.
As a Java dev, I only have to snap my fingers and get 20 job offers... I then only have to pick the one that I like most.
Re: (Score:2)
On site for the most part, although working one day remote a week is often an option. If you work only remote, you are competing with developers from countries where living expenses are low, wages are low and/or taxes are low or all three. You can't win that.
My situation applies to Europe, where everyone and his dog wants an App, a Website or whatever. I do freelance work there as it pays far better. In the US it seems to be the same (I haven't seen a company that isn't hiring devs), unfortunately going
Production Ready? (Score:4, Funny)
"JDK 9 is a production-ready implementation..."
It's about time that they're ready for production.
Re: (Score:2)
"JDK 9 is a production-ready implementation..."
It's about time that they're ready for production.
Meh, their Weblogic middleware isn't Java8 ready yet. There is a lot of middleware and turnkey COTS systems out there that will simply not work if you move it to JDK 8 because of unknown regressions between JDK versions.
It is great to move to the latest JDK versions for fresh development using barebone containers,though.
Re: (Score:1)
Stop hiring H1Bs to write your code then. Use third world developers, get third world software.
Re: (Score:2)
The fault is with whoever built that software, then with whoever hired those people to build that software, followed by whoever decided to buy this software, followed by YOU who allowed this shit to be installed on their systems without proper auditing. Grow a backbone.
Re: (Score:2, Insightful)
Java will outlive both you and I.
Re: (Score:1)
LOL.
Ask a webdeveloper from last decade? Netscape WAS FAAAAR worse than IE when it came to standards compliancy. IE 6 was the better browser. It was mean and crashed less .... no I am not making this shit up either.
Those were dark days for the web in it's infancy. IE introduced ajax and CSS. By freezing it web developers created crud which only worked on it after so long accumulated to the point where enterprise computing had to stick with it as the newer versions were too secure and standards compliant to
Re: (Score:1)
Come on. Do you really think Sun did better by the time they released Java 6? That indeed looked a deprioritized project. But not what Oracle did with Java 8 and 9, that came with lots of changes and improvements.
Of course Java is a platform used in quite a lot of important stuff, so don't expect releases every 2 months breaking everything like Swift or Python. It's just a different league.
Re: (Score:2)
Ironically, it was not that per say which doomed IE.
It was incompatible with it's own bugs and security which when addressed broke all the ancient crud from the XP era. This is why corporations stuck with Java 6,7 as well as IE 6 for many many years well into 2013 when Windows 7 brought htem out kicking and screaming requiring rewritting everything.
Java is incompatible with itself which is why no one cares about the newer. They want legacy stuff working forever with all the security holes intacted to run Pe
People called Romanes they go the house? (Score:2)
Not that for each speak? WTF is that supposed to mean?
This is a Java thread, don't go bringing Python into it.
Re: (Score:2)
Java's entrenchment is so vast in the enterprise world that about the only competitor is COBOL. It isn't an Internet Explorer, it literally is the 21st century version of Cobol, and will be around just as long.
Re: (Score:2)
I heard if you keep repeating something long enough, it actually becomes true!
Only one feature would actually matter (Score:1)
Can it run ALL code and applets written for ALL previous java implementations? No? Then come back when its done.
Re: (Score:3)
There isn't a single language for which this is true, unless that language only has a 1.0 version and never patched any security holes. Do you want that security exploit that worked on Java 1.0 to work on Java 9? Perhaps you do depending on what business your in, but the rest of the world doesn't.
Java is probably *the* most backwards compatible language ever build, and they didn't make an exception with Java 9. So yes, I do expect it to run almost everything that was ever build for it.
In the cases it doe
Debian issues (Score:1)
I use Java for two reasons. First, I teach and our school gradebook application is written in Java (this is a godsend, because it lets me use Linux 100% at work). Second, I teach AP CS and Java is the current language. OpenJDK works well (and it actually works for the gradebook application too, although it seems a bit buggier at times), but I do like having the Oracle JDK because it's what most of the students have (they are mostly running Windows/macOS). Very rarely (about once every couple of years) we
Re: (Score:2)
The high DPI fix is for Swing, so it would depend on the UI toolkit used, but also on how those programs were written (if they did anything with fixed amounts of pixels, that won't scale). SWT already runs fine in high DPI (see Eclipse) and JavaFX does as well.
I'm sure a Debian package will be along shortly for Java 9, but yes, I agree, using the Ubuntu one should be reasonably safe, especially since Java is pretty much self contained and only hooks into the underlying OS at low levels (threading, I/O, etc