I'm torn over this because a lot of the features are quality of life improvements, but is it too fast?
> but is it too fast?
It is not.
A categorized list of all Java and JVM features since JDK 8 to 16
11–20 of 243 posts
Re: A categorized list of all Java and JVM features since JDK 8 to 16
#12I'm torn over this because a lot of the features are quality of life improvements, but is it too fast?
A lot of things are coming straight from C#, so it’s battle-tested there before inclusion I guess.
Re: A categorized list of all Java and JVM features since JDK 8 to 16
#13Java gets a bad rap from people that used it late 90's through early 2000's and got burned out by XML and design pattern heavy frameworks but its a lovely language that with a little discipline can be used to create very lean looking code.
Go is one of the HN darling languages and I work in Go everyday for work (and generally like it), but I really wish I could reach for Java most days.
Re: A categorized list of all Java and JVM features since JDK 8 to 16
#14Waiting for project loom [1] [1] https://openjdk.java.net/projects/loom/
I am unreasonably excited by Loom, for two reasons:
1. I cannot wrap my head around library-based reactive systems. I have tried and tried and continue to try. But they're like some of the original Go4 design patterns: they exist to solve the language, not the problem. Loom's promise to make steam-powered linear code behave mostly like a fully-dressed reactive library system is extremely welcome.
2. Structured concurrency. Among the entries on the thick tablet of hatreds of Golang that I carry upon my heart, mystery action at a distance due to go(to) routines appears infrequently but painfully. Like so many Go features they conspire against composability and testability. Structured concurrency looks like an escape from the madness. Please let it be true.
Re: A categorized list of all Java and JVM features since JDK 8 to 16
#15Is it in the realm of possibilities that Java will someday have runtime generics support (instead of type erasure)? It's the most frustrating aspect of the language because you can't use basic Java features like method overloading with them. Also, I don't understand how people use the `Optional
`..? Is there a way to use method overloading with it? `ErasedType` could be _anything_ at runtime, doesn't sound fun. Besides all references types are already nullable/(optional)...
so what's the point?
Re: A categorized list of all Java and JVM features since JDK 8 to 16
#16I'm torn over this because a lot of the features are quality of life improvements, but is it too fast?
A lot of things are coming straight from C#, so it’s battle-tested there before inclusion I guess.
I read an article that said that this is intentional- they wait until other languages shake out features, and take it slow so they get it right.
Re: A categorized list of all Java and JVM features since JDK 8 to 16
#17Java gets a bad rap from people that used it late 90's through early 2000's and got burned out by XML and design pattern heavy frameworks but its a lovely language that with a little discipline can be used to create very lean looking code. Go is one of the HN darling languages and I work in Go everyday for work (and generally like it), but I really wish I could reach for Java most days.
“Java is a big DSL to transform XML into stacktraces” — so was the joke at the time when domain-specific languages were the hype.
This, and the FizzBuzz, Enterprise Edition: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
More seriously, what are you missing in Go that is well-done in Java? I assume verbosity of the code is still the defining characteristic of Java?
Re: A categorized list of all Java and JVM features since JDK 8 to 16
#18One of the primary features I'm holding out hope for eventually making it into the language is ValueTypes: http://cr.openjdk.java.net/~jrose/values/values-0.html and the current Valhalla Project: https://wiki.openjdk.java.net/display/valhalla/Main The simplest example of why this would be valuable (edit: this was not an intentional pun), the Optional type could become stack based, such that you could ensure that the…
I am not sure I understand, why would you want Optional type to never be null? Isn't it being null sometimes — the whole point?
Re: A categorized list of all Java and JVM features since JDK 8 to 16
#19Is it in the realm of possibilities that Java will someday have runtime generics support (instead of type erasure)? It's the most frustrating aspect of the language because you can't use basic Java features like method overloading with them. Also, I don't understand how people use the `Optional `..? Is there a way to use method overloading with it? `ErasedType` could be _anything_ at runtime, doesn't sound fun. Besid…
I wish we just had non-nullable types...
Re: A categorized list of all Java and JVM features since JDK 8 to 16
#20Java gets a bad rap from people that used it late 90's through early 2000's and got burned out by XML and design pattern heavy frameworks but its a lovely language that with a little discipline can be used to create very lean looking code. Go is one of the HN darling languages and I work in Go everyday for work (and generally like it), but I really wish I could reach for Java most days.
>got burned out by XML and design pattern heavy frameworks
Most succinct summary I have heard lately :) I think a good bunch of blame is also on the developers who blindly adhere to said patterns. https://www.quora.com/What-are-the-most-ridiculous-Java-clas... to rest the case.