<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nick Ebbitt on foojay.io - Friends of OpenJDK</title><link>https://foojayio.github.io/website/today/author/nick-ebbitt/</link><description>Articles written by Nick Ebbitt on foojay.io - Friends of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 31 Jul 2024 06:01:49 +0000</lastBuildDate><atom:link href="https://foojayio.github.io/website/today/author/nick-ebbitt/index.xml" rel="self" type="application/rss+xml"/><item><title>JManc 2024 Trip Report</title><link>https://foojayio.github.io/website/today/jmanc-2024-trip-report/</link><pubDate>Wed, 31 Jul 2024 06:01:49 +0000</pubDate><guid>https://foojayio.github.io/website/today/jmanc-2024-trip-report/</guid><description>&lt;h2 id="tldr"&gt;tl;dr&lt;/h2&gt;
&lt;p&gt;Great day, great people, great discussions and great team of &lt;em&gt;dis-organisers&lt;/em&gt;!&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Whoever comes are the right people!&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Thanks to all who attended, it&amp;rsquo;s down to each and every one of you that JManc Unconference 2024 was a success!&lt;/p&gt;
&lt;p&gt;See you next year! 😀&lt;/p&gt;
&lt;h2 id="intro"&gt;intro&lt;/h2&gt;
&lt;p&gt;In January this year we decided to test the interest of the Manchester Java Community on whether they were up for another edition of the &lt;a href="https://jmanc.org/" target="_blank" rel="noopener noreferrer"&gt;JManc Unconference&lt;/a&gt;
. We sent out a survey to our members and from the responses received there was unanimous support for to us to run it again. This gave &lt;a href="https://www.linkedin.com/in/jsbullock/" target="_blank" rel="noopener noreferrer"&gt;Jon Bullock&lt;/a&gt;
, &lt;a href="https://www.linkedin.com/in/david-underwood-6b929858/" target="_blank" rel="noopener noreferrer"&gt;Dave Underwood&lt;/a&gt;
 and I the motivation we needed to put plans into motion for the 3rd edition of JManc Unconference!
&lt;img src="https://www.nickebbitt.com/blog/2024/07/20/jmanc-2024/jmanc-2024.png" alt="JManc 2024" loading="lazy"&gt;
&lt;/p&gt;</description></item><item><title>JManc Unconference 2024</title><link>https://foojayio.github.io/website/today/jmanc-unconference-2024/</link><pubDate>Tue, 21 May 2024 14:08:14 +0000</pubDate><guid>https://foojayio.github.io/website/today/jmanc-unconference-2024/</guid><description>&lt;p&gt;&lt;a href="https://foojayio.github.io/website/www.jmanc.org" title="JManc Unconferece"&gt;&lt;img src="https://jmanc.org/assets/images/jmanc-logo.png" alt="JManc Unconferece" title="JManc Unconferece" loading="lazy"&gt;
&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The Manchester Java Community are delighted to announce the return of JManc Unconference on Friday 28th June 2024!&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s been a few years since we last hosted JManc, and a lot has changed in the world, but one thing we&amp;rsquo;ve learned in the Manchester Java Community is that in-person events are what we love the most. JManc provides another opportunity for us to get together with like-minded people from the Java community.&lt;/p&gt;</description></item><item><title>The Story of a Java 17 Native Memory Leak</title><link>https://foojayio.github.io/website/today/the-story-of-a-java-17-native-memory-leak/</link><pubDate>Tue, 13 Sep 2022 08:15:53 +0000</pubDate><guid>https://foojayio.github.io/website/today/the-story-of-a-java-17-native-memory-leak/</guid><description>&lt;h2 id="context"&gt;Context&lt;/h2&gt;
&lt;p&gt;When Java 17 was released, we (the platform team at &lt;a href="https://careers.autotrader.co.uk/" target="_blank" rel="noopener noreferrer"&gt;Auto Trader&lt;/a&gt;
 where I was working at the time) were fairly quick to provide a new Docker base image to allow our developers to gain the benefits of the new goodness in the JDK available since Java 11, the previous LTS version.&lt;/p&gt;
&lt;p&gt;Over the course of a few years, we&amp;rsquo;ve standardised the way the JVM is configured out of the box for any new applications that make use of the base image. In general, this provides product teams with a good default starting point from which to get up &amp;amp; running quickly with any new service they plan to deploy.&lt;/p&gt;</description></item></channel></rss>