<story><title>Java 10 and beyond – a look at the potential language change</title><url>https://zeroturnaround.com/rebellabs/java-10-and-beyond-a-look-at-the-potential-language-change/</url></story><parent_chain><item><author>zmmmmm</author><text>The rapid release cycle is going to pose challenges downstream for all the people developing tooling and other aspects of the ecosystem which are not used to moving that fast (eg: Groovy still grappling with the module changes to Java9, let alone 10 or 11). While we all griped about it for many years, the slow pace of Java evolution was in some ways one of it&amp;#x27;s biggest features. I am curious to see whether the community starts to move fast too, or if actually what happens is that people completely ignore the non-LTS versions and we actually get an effective release cadence of 2-3 years or so in practice.</text></item></parent_chain><comment><author>repolfx</author><text>If you can make it past 8 to 9 then 9 to 10 and 10 to 11 are much easier.&lt;p&gt;The reason the community is struggling with Java 8 to Java 9 is that 9 broke a TON of stuff. It&amp;#x27;s not backwards compatible at all. Basically every non-trivial app broke. The breakages are mostly in things that were technically never guaranteed, even trivial things like the version number went from &amp;quot;1.8&amp;quot; to &amp;quot;9&amp;quot; which makes sense but broke loads of programs that tried to parse the version.&lt;p&gt;But some of it is also just bad processes and habits in the community. Some of the programs that broke due to the version number change from 8 to 9 broke &lt;i&gt;again&lt;/i&gt; from 9 to 10 just months later because they had enums that listed every possible version.... their codebase literally encoded the assumption that new major java releases hardly ever happened!</text></comment>
<story><title>Java 10 and beyond – a look at the potential language change</title><url>https://zeroturnaround.com/rebellabs/java-10-and-beyond-a-look-at-the-potential-language-change/</url></story><parent_chain><item><author>zmmmmm</author><text>The rapid release cycle is going to pose challenges downstream for all the people developing tooling and other aspects of the ecosystem which are not used to moving that fast (eg: Groovy still grappling with the module changes to Java9, let alone 10 or 11). While we all griped about it for many years, the slow pace of Java evolution was in some ways one of it&amp;#x27;s biggest features. I am curious to see whether the community starts to move fast too, or if actually what happens is that people completely ignore the non-LTS versions and we actually get an effective release cadence of 2-3 years or so in practice.</text></item></parent_chain><comment><author>jldugger</author><text>Hopefully the faster release cycle is tied with smaller changesets per release.</text></comment>