17 Nov 2026
DZone Java Zone
Pitching Kotlin: An Engineering Leader's Guide to Legacy Modernization
I've been on both sides of the Kotlin conversation: the engineer making the case, and the architect who reviews it and recommends a direction before a committee decides. On the reviewing side, the pattern is predictable: most Kotlin pitches die in the second meeting. A tech lead shows up with a list of syntax wins, managers or architects ask about migration risk, and the conversation ends with "we'll revisit this next quarter." The technical case for Kotlin is usually sound, but the pitch stalls because it argues from developer preference, while engineering leaders approve migrations based on cost and risk. I've spent a large part of my career on systems where a defect moves real money (I talked about what that means for Kotlin code at KotlinConf 2026), and when I wrote the Kotlin Enterprise Playbook, I ran this exact argument through a financial model across mobile, edge, and backend domains. The proposals that held up were the ones that priced cost and risk honestly, including the cases where the answer was "not here."
This guide is the framework I use when I review these proposals. Decide domain by domain, solution by solution, instead of organization-wide. Make the cost of the status quo measurable. Price the migration, including the parts nobody budgets for. Place gates where decisions stop being reversible. Make sure the people who carry the risk own the outcome. Kotlin is the worked example, but the same framework applies to any large technical migration, whether it's a language, a framework, or a data platform.
17 Nov 2026 4:45pm GMT
Reading GC Logs: Memory Leak or Undersized Heap?
It's 3 AM. Your phone buzzes. The pipeline that's been running fine for six hours just died with java.lang.OutOfMemoryError: Java heap space, and the on-call channel wants to know: is this a leak, or did we just under-size the executors? Someone suggests bumping memory from 8g to 12g and going back to sleep. Someone else suspects the new dedup cache from last week.
The GC log won't settle that argument by itself - but it tells you which diagnostic to run next, and that's worth more than a guess at 3 AM.
17 Nov 2026 4:00pm GMT
16 Nov 2026
DZone Java Zone
Spring Boot's Hidden Secret for Configuration: EnvironmentPostProcessor
Spring Boot's Quiet Hook for Shipping Configuration: EnvironmentPostProcessor
Hi everyone! This is Mikhail Polivakha, technical lead of the Axelix project (an open-source product that helps you find common problems and inefficiencies in Spring Boot applications - btw, give us a star!).
I want to talk about a piece of Spring Boot that a lot of people have never touched directly, yet almost everyone has bumped into the problem it solves. Let me start with a scene that I suspect will feel familiar:
16 Nov 2026 7:00pm GMT
25 Aug 2026
Lua: news
Lua 5.4.9 released
Lua 5.4.9 has been released. It fixes all known bugs in Lua 5.4.8.
25 Aug 2026 11:00am GMT
04 Aug 2026
Lua: news
Lua 5.5.1 released
Lua 5.5.1 has been released. It fixes all known bugs in Lua 5.5.0.
04 Aug 2026 12:38am GMT
20 Feb 2026
Lua: news
Lua becomes an SPI associated project
Lua is now an SPI associated project.
20 Feb 2026 11:15am GMT