<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fahim Farook on foojay.io - Friends Of OpenJDK</title><link>https://foojay.io/today/author/fahim-farook/</link><description>Articles written by Fahim Farook on foojay.io - Friends Of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 19 Jun 2026 08:15:28 +0000</lastBuildDate><atom:link href="https://foojay.io/today/author/fahim-farook/index.xml" rel="self" type="application/rss+xml"/><item><title>Where production policy belongs: building Eliya in public</title><link>https://foojay.io/today/where-production-policy-belongs-building-eliya-in-public/</link><pubDate>Fri, 19 Jun 2026 08:15:28 +0000</pubDate><guid>https://foojay.io/today/where-production-policy-belongs-building-eliya-in-public/</guid><description>&lt;p&gt;This is an argument about where production intent belongs in a managed runtime, and the OpenJDK distribution we built to act on it - Eliya, an opinionated, compliance-conscious OpenJDK distribution. This is the first article in a series. The later parts are engineering: reproducible builds, the glibc floor, release signing, the one source patch we shipped. This part is the thesis they all serve.&#10;&lt;img src="https://foojay.io/today/where-production-policy-belongs-building-eliya-in-public/jvm-behaviour-space-8d14d74a.png" alt="" width="813" height="375" loading="lazy" decoding="async"&gt;&lt;/p&gt;&#10;&lt;p&gt;Every configurable system has two spaces. The configuration space: every behaviour you can reach by setting the knobs the system already exposes. And there&amp;rsquo;s the implementation space: behaviour that only exists if someone goes in and changes the internals.&lt;/p&gt;</description></item></channel></rss>