7 ms·

Java 9 Enters First Bug Fixing Round

61 points by youknownothing 10y ago

sgt 10y ago
Java's quite exciting these days. I wish I could say the same about the state of Java EE though.
- on_and_off 10y ago
  I wish it would mean anything for android ... at this point I am all in the kotlin boat though : brings better solutions than the new versions of javas to its language design weaknesses (breaking code compatibility is a great asset for kotlin) is useable right now on android, not in 5 years.
  - smrtinsert 10y ago
    Something exciting for Android? Just look for the latest component-replacing-fragment of the day, I'm sure hundreds came out yesterday.
    - on_and_off 10y ago
      That's not exactly exciting .. A part of the android community has been complaining about fragments for years that's not really news.
- Traubenfuchs 10y ago
  Java EE is dead. Long live Spring (Boot)! They are planning to wait nearly one more year until Java EE 8 is released. This is unacceptable in todays fast moving world.
  - sgt 10y ago
    VertX (vertx.io) is rapidly becoming my choice of replacing Java EE.
    - Traubenfuchs 10y ago
      To someone who is primarily working with database driven applications this looks really bad compared to what spring-data offers: https://github.com/vert-x3/vertx-examples/blob/master/jdbc-examples/src/main/java/io/vertx/example/jdbc/transaction/JDBCExample.java https://github.com/vert-x3/vertx-examples/blob/master/jdbc-e... What is the appeal to you?
    - youknownothing 10y ago
      If you haven't already, may want to take a look at MicroProfile, an initiative to provide a standard reference platform for microservices using Java EE technologies (wherever possible). It can probably give you what you have, with the added benefit of portability.
- youknownothing 10y ago
  Although still young, and technically not Java EE, the MicroProfile initiative seems pretty promising. That might lighten things up.
- needusername 10y ago
  I hope they bring a modular Java EE 9 that allows you to pick and choose Java EE APIs. I'm not confident but one can still hope.
struppi 10y ago
Good! I am really looking forward to jshell, yet I appreciate that the Java team at Oracle is taking it's time to get this right. With their very strict backwards compatibility requirements (still compatible with Java 1.0 AFAIK), everything they release to the public, they must maintain forever. Side note: Can somebody please write a concise tutorial about how to use the new features (like this awesome Java 8 tutorial: https://github.com/winterbe/java8-tutorial https://github.com/winterbe/java8-tutorial )? If you do, contact me. I would love to help out, but I don't have much time at the moment...
- needusername 10y ago
  > I appreciate that the Java team at Oracle is taking it's time to get this right Except they don't. Everything but Jigsaw has been ready for a year and Jigsaw is still not ready. http://www.sonatype.org/nexus/2017/01/23/advice-for-jigsaw-regarding-auto-modules/ http://www.sonatype.org/nexus/2017/01/23/advice-for-jigsaw-r... http://wildfly.org/news/2016/12/12/Jigsaws-Missing-Pieces/ http://wildfly.org/news/2016/12/12/Jigsaws-Missing-Pieces/ > With their very strict backwards compatibility requirements (still compatible with Java 1.0 AFAIK) When I checked a few weeks ago Jigsaw broke a lot of reflection code. It's debatable how much of this was a published API but a lot of things broke. I don't know how many of these changes were rolled back.
Traubenfuchs 10y ago
Java 8 brought us lambda methods and streams that allow Java as a language to somewhat compete on the same stage as C#. I use them on a daily basis and they radically changed the way I do some things. It was a revolution for the Java world. What killer feature does Java 9 bring us? Jigsaw looks to me like a mere organizational feature, something I don't want to spend my time with unless I have to to get things working. Besides that, private interface methods are a nice idea, but I have never missed them before. Everything else leaves me unimpressed.
- coldtea 10y ago
  >Jigsaw looks to me like a mere organizational feature, something I don't want to spend my time with unless I have to to get things working. It's not for your typical use cases, it's for people running Java in lesser devices. That said, a REPL and HTTP 2.0 support are big in themselves. And the revised process management API too. Not every release needs to be a "revolution".
  - mkesper 10y ago
    HTTP/2 is not officially in as the article says, only accessible via incubator.
  - Traubenfuchs 10y ago
    Official Java REPL is not big. I know I will never use it and I don't know anyone who will. Those who get excited by live scripting/REPL probably won't be using Java. In any case, there is even a Java REPL solution available already if you really miss it. (java-repl) "Native" HTTP 2.0 support is nice and something that's expected to arrive eventually but also not big. A lot of people currently use alternative HTTP libraries anyways. As a Spring developer I usually use Resttemplate to do HTTP/REST calls and you can feed that with a RequestFactory that produces HTTP2 enabled requests, like OkHttp and Jetty. I don't know about Apache HttpClient. As for the process management API: That's actually quite nice, but the last time I touched processes was when I was writing horrible winforms applications years ago. Yes, certainly, not every release needs to be a revolution, but if you ask "What does it add that I will enjoy to use on a daily basis?" and the answer is "Nothing really, but take a look at ..." it's a bit disappointing. Some Java 10 features look like they could be big. If Java 9 is the Windows Vista of Java, Java 10 hopefully will be the Windows 7. (;
virtualwhys 10y ago
In other words, Java 10, godspeed.
exabrial 10y ago
Jigsaw is an incredible language feature! Can't wait to use it.

sgt 10y ago

Java's quite exciting these days. I wish I could say the same about the state of Java EE though.

on_and_off 10y ago
I wish it would mean anything for android ... at this point I am all in the kotlin boat though : brings better solutions than the new versions of javas to its language design weaknesses (breaking code compatibility is a great asset for kotlin) is useable right now on android, not in 5 years.
- smrtinsert 10y ago
  Something exciting for Android? Just look for the latest component-replacing-fragment of the day, I'm sure hundreds came out yesterday.
  - on_and_off 10y ago
    That's not exactly exciting .. A part of the android community has been complaining about fragments for years that's not really news.
Traubenfuchs 10y ago
Java EE is dead. Long live Spring (Boot)! They are planning to wait nearly one more year until Java EE 8 is released. This is unacceptable in todays fast moving world.
- sgt 10y ago
  VertX (vertx.io) is rapidly becoming my choice of replacing Java EE.
  - Traubenfuchs 10y ago
    To someone who is primarily working with database driven applications this looks really bad compared to what spring-data offers: https://github.com/vert-x3/vertx-examples/blob/master/jdbc-examples/src/main/java/io/vertx/example/jdbc/transaction/JDBCExample.java https://github.com/vert-x3/vertx-examples/blob/master/jdbc-e... What is the appeal to you?
  - youknownothing 10y ago
    If you haven't already, may want to take a look at MicroProfile, an initiative to provide a standard reference platform for microservices using Java EE technologies (wherever possible). It can probably give you what you have, with the added benefit of portability.
youknownothing 10y ago
Although still young, and technically not Java EE, the MicroProfile initiative seems pretty promising. That might lighten things up.
needusername 10y ago
I hope they bring a modular Java EE 9 that allows you to pick and choose Java EE APIs. I'm not confident but one can still hope.

Good! I am really looking forward to jshell, yet I appreciate that the Java team at Oracle is taking it's time to get this right. With their very strict backwards compatibility requirements (still compatible with Java 1.0 AFAIK), everything they release to the public, they must maintain forever. Side note: Can somebody please write a concise tutorial about how to use the new features (like this awesome Java 8 tutorial: https://github.com/winterbe/java8-tutorial https://github.com/winterbe/java8-tutorial )? If you do, contact me. I would love to help out, but I don't have much time at the moment...

needusername 10y ago
> I appreciate that the Java team at Oracle is taking it's time to get this right Except they don't. Everything but Jigsaw has been ready for a year and Jigsaw is still not ready. http://www.sonatype.org/nexus/2017/01/23/advice-for-jigsaw-regarding-auto-modules/ http://www.sonatype.org/nexus/2017/01/23/advice-for-jigsaw-r... http://wildfly.org/news/2016/12/12/Jigsaws-Missing-Pieces/ http://wildfly.org/news/2016/12/12/Jigsaws-Missing-Pieces/ > With their very strict backwards compatibility requirements (still compatible with Java 1.0 AFAIK) When I checked a few weeks ago Jigsaw broke a lot of reflection code. It's debatable how much of this was a published API but a lot of things broke. I don't know how many of these changes were rolled back.

Traubenfuchs 10y ago

Java 8 brought us lambda methods and streams that allow Java as a language to somewhat compete on the same stage as C#. I use them on a daily basis and they radically changed the way I do some things. It was a revolution for the Java world. What killer feature does Java 9 bring us? Jigsaw looks to me like a mere organizational feature, something I don't want to spend my time with unless I have to to get things working. Besides that, private interface methods are a nice idea, but I have never missed them before. Everything else leaves me unimpressed.

coldtea 10y ago
>Jigsaw looks to me like a mere organizational feature, something I don't want to spend my time with unless I have to to get things working. It's not for your typical use cases, it's for people running Java in lesser devices. That said, a REPL and HTTP 2.0 support are big in themselves. And the revised process management API too. Not every release needs to be a "revolution".
- mkesper 10y ago
  HTTP/2 is not officially in as the article says, only accessible via incubator.
- Traubenfuchs 10y ago
  Official Java REPL is not big. I know I will never use it and I don't know anyone who will. Those who get excited by live scripting/REPL probably won't be using Java. In any case, there is even a Java REPL solution available already if you really miss it. (java-repl) "Native" HTTP 2.0 support is nice and something that's expected to arrive eventually but also not big. A lot of people currently use alternative HTTP libraries anyways. As a Spring developer I usually use Resttemplate to do HTTP/REST calls and you can feed that with a RequestFactory that produces HTTP2 enabled requests, like OkHttp and Jetty. I don't know about Apache HttpClient. As for the process management API: That's actually quite nice, but the last time I touched processes was when I was writing horrible winforms applications years ago. Yes, certainly, not every release needs to be a revolution, but if you ask "What does it add that I will enjoy to use on a daily basis?" and the answer is "Nothing really, but take a look at ..." it's a bit disappointing. Some Java 10 features look like they could be big. If Java 9 is the Windows Vista of Java, Java 10 hopefully will be the Windows 7. (;

virtualwhys 10y ago

In other words, Java 10, godspeed.

exabrial 10y ago

Jigsaw is an incredible language feature! Can't wait to use it.