5 ms·
Still on Java 8 at work :-/
by JulianMorrison 6y ago
Still on Java 8 at work :-/
- bartvk 6y agoWhat’s the reason for that?
- BoyRobot777 6y agoEvery thread about new Java version has the same comment all the time. Why share it? What kind of response do you seek?
- matsemann 6y agoI think it's interesting to discuss how many are stuck on java8. It was a long time many of us were stuck on java6 or 7, and finally got up to java8. But then when 9, 10 and 11 came no one made an effort to upgrade. Why? And now we're at 15 and people are starting to feel the heat. We only migrated our main service from 8 to 15 a month ago (AWS deprecation), but still have lots of 8 code laying around (luckily some of the container-features were backported)
- JulianMorrison 6y agoSpeaking from personal experience, the creators of most of the recent JDK versions have made very poor efforts to explain the changes, it's mostly just a list of RFC type documents, and who has time? An example of something that compares favourably would be Go, where they always blog about the changes, and there's easy to find official language documentation (and not just autogenerated API docs).
- kaba0 6y agoHave you tried for example the linked article with all the JEPs listed with lengthy descriptions? And with links to relevant mailing lists if it didn’t satisfy your curiosity?
- JulianMorrison 6y agoI just yesterday took the time to go and read through them. And I still consider it awful UI. - A list of links is not a summary. The list is too short, reading every individual linked document is too long. The format of JEPs tends to bury the lede. As such it feels like wading through mud. - Changes that affect the programmer experience are mixed at random with changes that affect internal details of the implementation. - Changes that introduce experimental features are mixed at random with changes that are final.
- cesarb 6y ago> I think it's interesting to discuss how many are stuck on java8. [...] But then when 9, 10 and 11 came no one made an effort to upgrade. Why? A lot of things broke in Java 9, which was short-lived (both it and Java 10 lasted only six months each), and then Java 11 broke many other things (for instance, it removed all of J2EE). As late as last year, I was still seeing changes in libraries to fix issues with Java 9 or later. It's not that no one made an effort to upgrade, it's that it was a lot of effort, and often required upgrading to later versions of libraries, which have their own breaking changes.
- vips7L 6y agoIn my experience mst of these changes are simple to add to your projects pom or build.gradle. For instance the removal of the jaxb xml runtime is a simple 1 liner to your project: runtimeOnly 'org.glassfish.jaxb:jaxb-runtime:2.3.2'
- cferr 6y agoEight's JVM still ships with Minecraft, so that's not necessarily a bad thing. It's battle-proven.
- stonemetal12 6y agoAmazon's version or the for a while now EOL Oracle version? Maybe push to upgrade to something supported :)
- JulianMorrison 6y agoA mad scramble to switch to OpenJDK before the Oracle license becomes inconvenient.
- randomopining 6y ago8 is still “modern” Java right? 11 didn’t add a ton ton for most developers.
- brabel 6y agoI'd say that now with 15 adding records and instanceof pattern, Java 8 is finally looking pretty dated! You're also missing out on var and switch expressions, which are very visible features (as are records and instanceof patterns), so the difference should be obvious between a Java 8 codebase and a Java 15 one.
- randomopining 6y agoVar and switch were the biggest from Java 11, along with modules and the new GCs?
- BoyRobot777 6y agoI very much like text blocks as well. SQL/JSON can be finally understandable without all the "\n" +
- dehrmann 6y agoFor those who have upgraded, I assume Jigsaw is the main concern?
- aogl 6y agoAt a bank, and yes, us too!
- EdwardDiego 6y agoI've been using Maven and Gradle's toolchains functionality to move individual apps to Java >8 without breaking the legacy apps, works pretty well.