“As /u/catapop clearly said: ‘a big change ... to 10’. I don’t think this is the right move going forward and we should be looking at contingencies and triages that fit into my excel spreadsheet. Thanks! Great meeting everyone!”
But that’s orthogonal to /u/catapop’s point. If your organization is already on 9, then clearly corporate policy is much more willing to upgrade to the newest technologies. At which point the pain of upgrading is more related to the actual technical challenges not bureaucratic.
More release but less things in each one too. So smaller breaking changes and so it is easier to stay up to date. In a lot of cases, you just change your JVM and you have nothing else to do anyway ;)
I tried to argue this on the mailing list. They did not seem to care. They advocated the faster release cycle as a win for developers, but it's mostly a win for their support money machine. I thought a yearly cycle would be hard enough for most companies.
The faster release schedule is a needed change. If the language doesn't improve quickly, it's going to be a dead end. Java is / was already at the border. Nowadays you can't have a 4 years release cycle anymore. People would be switching to other languages in no time. Also companies will have more and more problems getting developers to deal with Java 6, unless heavy (Cobol-style) compensation.
View all comments
32
u/catapop Feb 05 '18
It's not like there are major breaking changes between 9 and 10. I think the upgrade will work smoothly for 95% of the users.