![]() InfoQ: What Java build are you using? Is it the Microsoft one? If so, what was the inspiration to use it? The response has been overwhelmingly positive it really matters to their developer productivity to have access to the latest features! One interesting thing was that we weren’t sure how quickly the mod community would take to using the new language features. We didn’t have any failed expectations per se it’s been very successful. InfoQ: Was there something that you expected to happen once using Java 16, but didn’t? It’s worth upgrading from an operational perspective! Lots of performance gains out-of-the-box with start-up times from Application and Class Data Sharing, memory efficiency gains from String Deduplication in the G1 Garbage Collector, a smoother experience because there are fewer long pauses from GC, and a host of other small improvements. What improvements did you observe in comparison with the previous setup? InfoQ: You have been running JDK 16 in production for some time now. Once you get into the habit it’s a relatively small update cost for a large gain each time! Then you can incrementally update your dependencies and code to take advantage of the new features. We recommend that any serious Java shop sets up their CI/CD to onboard each major release. The earlier challenges in the migration came via moving from Java 8 to Java 11 due to the module system introducing stricter security controls around accessing JDK internals which some of our 3 rd party dependencies relied on at the time. InfoQ: Can you describe the migration process? How smooth was it? How long did the migration take?Īs we’d been keeping up-to-date with each major version, we avoided the big bang migration and so it wasn’t too difficult. We’re currently evaluating Java 17 with Microsoft, since it is an LTS release it makes sense that we’ll roll it out sometime in the future, but we’re not committing to a concrete date yet. It also gave our developers a boost in their productivity with new features like var, switch expressions, text blocks and more! Java 16 gave us significant out-of-the-box performance gains with regards to startup times, memory management and code execution. We’d been keeping up-to-date with each Java release version as it came out (on a separate branch from our main branch). InfoQ: What was the reasoning for migrating to Java 16, when Java 17 was just around the corner? Did you migrate to Java 17, or do you intend to? What was the version you migrated from? Given their head start with running Java 16 in production, InfoQ spoke to the Mojang team to better understand their experience and gains. This is even more interesting, as Minecraft is now part of Microsoft, hence it will use the newly developed JRE. Even though the release date was clearly set, the team at Minecraft decided to make the move earlier, migrating to JDK 16. The release bears the promise of out-of-the-box improved performance, as Application and Class Data Sharing (AppCDS) is among the new features, along with the improved performance of the new G1 Garbage Collector. Probably one of the things worth mentioning, especially in the Java world, is the release of JDK 17, the LTS version incorporating features like pattern matching for switches, a new vector API or sealed classes. With the year quickly coming to an end, whether we like it or not, we reflect on 2021.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |