Slashdot Mirror

← Back to Stories (view on slashdot.org)

Oracle Announces Java SE 9 and Java EE 8 (oracle.com)

Posted by msmash on from the dispatch dept.

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.

13 of 64 comments (clear)

  1. Maybe most popular... by TWX · · Score: 3, 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.

    --
    Do not look into laser with remaining eye.
    1. Re:Maybe most popular... by Anonymous Coward · · 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.

    2. Re:Maybe most popular... by jellomizer · · 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.
      You have .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.
      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.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    3. Re:Maybe most popular... by The+MAZZTer · · Score: 3, Informative

      .NET Core, which is pretty much .NET remade to be cross-platform, is also for Mac OS/Linux too now. And I won't be surprised if platform support increases in the future though I don't think they've announced any plans for that yet.

    4. Re:Maybe most popular... by MightyMartian · · Score: 4, 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.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    5. Re:Maybe most popular... by TWX · · Score: 2

      So they caught mono?

      --
      Do not look into laser with remaining eye.
    6. Re:Maybe most popular... by colablizzard · · Score: 2

      The most important thing is tooling. Java has got everything checkboxed for use in Corporate Environments. You want FIPS compliant crypto? You want static code analysis? You want tools to scan usage of open source libraries? You want tool to see if your developer copy pasted code from stack overflow? Everything is a Check Yes in Java, that too most of these tools are free and reputable. The Apache and OWASP foundations literally keep Java alive. The only problematic thing is their new EOL policy for Java SE. They have effectively killed the usage of the "free" Java SE in environments with the new EOL policy. To put it simply, one will need to constantly update to the latest major version http://www.oracle.com/technetw...

  2. Re:minus project valhalla :( by mccalli · · Score: 2

    I never really understand posts like this. "This is the one thing that would have kept me on Java". Why? Java is a tool like any other. You use it when you should, you don't use it when you shouldn't. After decades of existing, it's quite clear it doesn't actually need the Valhalla stuff. It would be nicer with it, but this is not an existential crisis.

  3. All 9 of us are thrilled by Billly+Gates · · Score: 3, 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.

    --
    http://saveie6.com/
    1. Re:All 9 of us are thrilled by jellomizer · · Score: 4, 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.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  4. Production Ready? by swsuehr · · Score: 3, Funny

    "JDK 9 is a production-ready implementation..."

    It's about time that they're ready for production.

  5. Re:Too little, too late by Anonymous Coward · · Score: 2, Insightful

    Java will outlive both you and I.

  6. Re:Only one feature would actually matter by swilver · · Score: 2

    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 doesn't (which I have not encountered in any decently engineered piece of Java) it probably is using undocumented functions or security exploits. I don't think I even want those to keep functioning.