<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Java on MacWorks</title><link>https://macworks.dev/tags/java/</link><description>Recent content in Java on MacWorks</description><generator>Hugo</generator><language>en</language><atom:link href="https://macworks.dev/tags/java/index.xml" rel="self" type="application/rss+xml"/><item><title>Hacker News</title><link>https://macworks.dev/docs/today/hackernews-2026-06-19/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://macworks.dev/docs/today/hackernews-2026-06-19/</guid><description>&lt;h1 id="hacker-news--2026-06-19"&gt;Hacker News — 2026-06-19&lt;a class="anchor" href="#hacker-news--2026-06-19"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;h2 id="top-story"&gt;Top Story&lt;a class="anchor" href="#top-story"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;&lt;a href="https://www.jvm-weekly.com/p/project-valhalla-explained-how-a"&gt;Project Valhalla, Explained: How a Decade of Work Arrives in JDK 28&lt;/a&gt;&lt;/strong&gt;
After 12 years and five discarded prototypes, Java is finally getting value classes in JDK 28, allowing developers to code like a class but execute with the memory density of a primitive. This is a tectonic shift for the JVM that fundamentally breaks the 1995 assumption that &amp;ldquo;every object has identity,&amp;rdquo; paving the way for flattened memory layouts without sacrificing object-oriented abstractions.&lt;/p&gt;</description></item></channel></rss>