3 ms·
I'm fully in support of defined, rolling release trains. 6 months is a good start considering where they're coming from. I feel like that's still slightly too l
by EddieRingle 9y ago
I'm fully in support of defined, rolling release trains. 6 months is a good start considering where they're coming from. I feel like that's still slightly too long though, and is one of the things I wish the Go team would change. The Go team's argument is that it takes time to fully test features before being able to release them, which I understand, but that's the whole point behind a multiple release train model.
But I digress. Faster Java & JVM updates will help Kotlin out as well moving forward. :)
- geodel 9y agoSince you consider 6 months too long, why would you not use nightly builds to grab new features as they land?
- virtualwhys 9y ago> Faster Java & JVM updates More likely faster updates will be to Java itself, while JVM enhancements will be limited to LTS. Pattern matching and data classes, for example, will arrive far sooner in Java than value types in the JVM.
- mreinhold 9y agoNo, JVM enhancements will not be limited to LTS. If anything it's best to merge them long before an LTS, so that they're well-baked in the LTS itself.
- virtualwhys 9y agoMy point is that "smaller" features like pattern matching and data classes will land in Java well before big ticket items like value types; not that JVM enhancements will be strictly limited to LTS. Of course, you have the inside word: when are value types coming to the JVM? Hopefully by Java 10.
- aardvark179 9y agoMinimal value types will arrive as an experimental feature at the VM level real soon now, language and library support will take a lot more work.
- hugi 9y agoGiggidy!