My workplaces have generally tried to stay up to date with new releases except for occasional legacy applications that are barely being updated anymore. However, that pattern remains to be seen with how much backwards compatibility is broken by Java 9.
On 22 April 2017 at 17:45, Ralph Goers <ralph.go...@dslextreme.com> wrote: > That is interesting. Where I work we moved straight from Java 6 to 8 and > skipped 7. That move was fairly painless. Despite me wanting to keep > compatibility with Java 7 here, everything I am using at work is running on > Java 8. But I anticipate the move to Java 9 is going to be fairly painful > for some of our applications as they will need to have lots of other > dependencies upgraded besides Java. > > Ralph > > > On Apr 22, 2017, at 2:59 PM, Gary Gregory <garydgreg...@gmail.com> > wrote: > > > > That's a given IMO. For my work projects, there is so much inertia > > anchoring to Java 7 for various reasons. > > > > One of the many fun things of FOSS for me is that things move faster than > > for work projects. > > > > So keeping on hearing that we must stay on Java 7 is not great. > > > > Yeah, there is the multi jar things and Java 9 thing but that is not the > > same as just moving to Java 8 plain and simple. > > > > Gary > > > -- Matt Sicker <boa...@gmail.com>
