The next interesting thing for the JVM is value types in Java 10. It may convince me to use it pre release.
I'd also add: Generic Specialization Reified Generics Native Function Calling Native Data Access New Data Layouts
This will not happen.
31–40 of 161 posts
Earlier quoted context omitted.
Here is the list: http://openjdk.java.net/projects/jdk9/
Am I missing properties? Dear god it's 2016, with Java8, and we still don't have real, language-defined properties? I mean you can use Lombok (and if you're not, you should be!), but that's something that really need to be built into the language. C# has them, Python has them, Ruby has them .. even other JVM languages like Scala have them! I'm really glad I get to do Scala development full time. Even with all the rec…
I am yet to work in a Java project where I am allowed to use any of them.
Regarding the properties I really don't get what is the big deal.
No one used to complain about C++ properties, that besides having to write accessors and mutator methods, one needs to declare them on the header files as well.
Or the first version of C# properties isn't much shorter than how it is done in Java, which is still required when extra logic needs to be implemented.
It is been a few years since I have done any Python, but don't do they require two separate functions that are then mapped to a property declaration?
Earlier quoted context omitted.
Most not totally old projects are on JDK8. Don't look at some crufty apache product, but look at medium size business apps... those have all been JDK8 for a while now.
> Don't look at some crufty apache product, but look at medium size business apps... What do you think those medium sized business apps are built off of if not things with JVM dependencies? It's not so simple.
Some things like Guava got more or less obsolete in JDK8.. so seeing it targeting JDK5.. doesn't really matter.
Also JDK5 stuff will work on JDK8.. so you can suck in all the JDK5 libraries you want, but still run a JDK8 project.
Earlier quoted context omitted.
I'd also add: Generic Specialization Reified Generics Native Function Calling Native Data Access New Data Layouts
>Reified Generics This will not happen.
http://www.oracle.com/technetwork/java/javase/community/jlss...
Earlier quoted context omitted.
>Reified Generics This will not happen.
This will happen: http://www.oracle.com/technetwork/java/javase/community/jlss...
https://www.youtube.com/watch?v=Tc9vs_HFHVo&list=PLX8CzqL3Ar...
Earlier quoted context omitted.
The vast majority of projects, at my employer. I personally upgraded several hundred JVMs running several dozen services - upgrading was simple and almost entirely painless. In addition to benefiting from the new features, being up-to-date is good for recruiting. You tell someone they'll be working with Java 6 and (in the absence of other evidence) they'll assume it's a legacy product suffering from chronic under-inv…
> they'll assume it's a legacy product suffering from chronic under-investment. Or Android.
Earlier quoted context omitted.
Here is the list: http://openjdk.java.net/projects/jdk9/
Am I missing properties? Dear god it's 2016, with Java8, and we still don't have real, language-defined properties? I mean you can use Lombok (and if you're not, you should be!), but that's something that really need to be built into the language. C# has them, Python has them, Ruby has them .. even other JVM languages like Scala have them! I'm really glad I get to do Scala development full time. Even with all the rec…
Earlier quoted context omitted.
Am I missing properties? Dear god it's 2016, with Java8, and we still don't have real, language-defined properties? I mean you can use Lombok (and if you're not, you should be!), but that's something that really need to be built into the language. C# has them, Python has them, Ruby has them .. even other JVM languages like Scala have them! I'm really glad I get to do Scala development full time. Even with all the rec…
> Scala, Groovy, Clojure, JRuby, etc. I am yet to work in a Java project where I am allowed to use any of them. Regarding the properties I really don't get what is the big deal. No one used to complain about C++ properties, that besides having to write accessors and mutator methods, one needs to declare them on the header files as well. Or the first version of C# properties isn't much shorter than how it is done in J…
I used to feel the same as you, then I dabbled with Rails. I think the deal is that in Java there is a lot of noise in the code. So, developing feels like you need to do a lot of yak shaving before you get to actually work on what you intend to build.
As a result, properties on their own isn't a big deal, but it's one more thing to slow you down and make things a little less enjoyable.
Earlier quoted context omitted.
This will happen: http://www.oracle.com/technetwork/java/javase/community/jlss...
Probably not at the language level. If you watch the Goetz talk you linked to he answers this at 50m36s. The bytecode and JVM will be able to represent riefied generics, but at the Java language level they'll still likely maintain erasure for Object types. https://www.youtube.com/watch?v=Tc9vs_HFHVo&list=PLX8CzqL3Ar...
Brian did not state they will never do it.
Also the other languages could take advantage of it anyway, even a reiffied version of Java for example.