<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Lombok on Swaranga Sarma</title><link>https://swaranga.dev/tags/lombok/</link><description>Recent content in Lombok on Swaranga Sarma</description><image><title>Swaranga Sarma</title><url>https://swaranga.dev/images/profile.jpg</url><link>https://swaranga.dev/images/profile.jpg</link></image><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 12 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://swaranga.dev/tags/lombok/index.xml" rel="self" type="application/rss+xml"/><item><title>Lombok is Still Relevant in the Age of Java Records</title><link>https://swaranga.dev/posts/on-lombok/</link><pubDate>Sun, 12 Jul 2026 00:00:00 +0000</pubDate><guid>https://swaranga.dev/posts/on-lombok/</guid><description>&lt;p>Every six months, like clockwork, a new JDK drops—and right on cue, the Java community&amp;rsquo;s ideological purity tests begin.&lt;/p>
&lt;p>The usual suspects crawl out to complain about Project Lombok. They argue that it does &amp;ldquo;weird hacks&amp;rdquo; to the &lt;code>javac&lt;/code> compiler, that it slows down upgrades, and that we don’t need it anymore because we have Records.&lt;/p>
&lt;p>I am a little tired of this constant principled stance against its usage. I am an application developer, not a compiler engineer. I&amp;rsquo;ve been using Lombok for roughly 15 years now, and I can clearly say its benefits massively outweigh its cons. I’m glad I don’t work with people who hold that dogmatic opinion, because at the end of the day, we are paid to deliver working software—not to coddle the compiler.&lt;/p></description></item></channel></rss>