<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mark Clarke on foojay.io - Friends of OpenJDK</title><link>https://foojayio.github.io/website/today/author/mark-clarke/</link><description>Articles written by Mark Clarke on foojay.io - Friends of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 22 Sep 2023 15:11:37 +0000</lastBuildDate><atom:link href="https://foojayio.github.io/website/today/author/mark-clarke/index.xml" rel="self" type="application/rss+xml"/><item><title>Mastering the Challenges of OpenJDK Migration.</title><link>https://foojayio.github.io/website/today/mastering-the-challenges-of-openjdk-migration/</link><pubDate>Fri, 22 Sep 2023 15:11:37 +0000</pubDate><guid>https://foojayio.github.io/website/today/mastering-the-challenges-of-openjdk-migration/</guid><description>&lt;p&gt;&lt;strong&gt;Ah, the halcyon days of Java development, where coding was king and APIs were the castle! From the nitty-gritty of the Java VM and garbage collection to the euphoria of leveraging new APIs, life was straightforward. With each Java update, you could expect nothing but improvements, a far cry from other ecosystems where every new version turned into a mini-project just to keep your codebase relevant. And with DevOps in the picture, version constraints felt like a thing of the past. Come 2017, Oracle promised us an accelerated release cycle, and life was good.&lt;/strong&gt;&lt;/p&gt;</description></item></channel></rss>