BellSoft
@bellsoft.bsky.social
88 followers 13 following 230 posts
Delivering #LibericaJDK: supported, #Java standard compatible binaries. Among Top-5 #OpenJDK contributors.
Posts Media Videos Starter Packs
bellsoft.bsky.social
The Steam Deck raffle is almost over 🎮
Join us at stand 24 today, Thursday Oct 9, at 16:15 for the winner announcement. Still a bit of time left if you haven’t joined yet – don’t miss your chance! #Devoxx
bellsoft.bsky.social
Looking for a legal performance boost for your #Java apps?
Tomorrow at #Devoxx Belgium, Dmitry Chuyko explores JVM “dopes”: Leyden, CRaC, Lilliput, Graal JIT, native images, fused JDKs.
How far can you go without rewriting code?
📅 Thu, Oct 9 • 12:55 • Room 5
bellsoft.bsky.social
We’re at booth 24 at #Devoxx Belgium. Lots of good conversations already – stop by if you want to talk #Java, performance, or containers.
bellsoft.bsky.social
Still on Java 8 or 11? You’re not alone.
Tomorrow at #Devoxx Belgium, @asm0dey.site (#BellSoft) and @jbaru.ch (@TuxCare) show how to make legacy #Java feel better – cleaner code, safer apps, faster runtime, without forced rewrites.
📅 Thu, Oct 9 • 13:50 • Room 7
bellsoft.bsky.social
#Java25 adds compact source files with instance main methods. No more complicated public static void main, just a clean entry point.
Perfect for PoCs and teaching.
bellsoft.bsky.social
Our team is at #Devoxx Belgium this week. You’ll find us at stand 24, where we’re discussing JVM performance, container efficiency, and #Java security with the community. We also have a Steam Deck raffle at the booth – stop by and take part!
Reposted by BellSoft
hillert.bsky.social
One important improvement in #Kamal 2.x is that #curl is no longer required for your #Docker images in order to perform health checks. That way way you can use slim base images, e.g. @bellsoft.bsky.social 's Alpaquita based image for Liberica #Java, e.g. jdk-25-cds-slim-musl ☕.
bellsoft.bsky.social
In Berlin this week? Don’t miss tomorrow’s talk at Berlin Expert Days 🎤
@asm0dey.site will show how #Java apps can start in just 5 ms – without native images – using #CRaC (Coordinated Restore at Checkpoint).
🗓️ Tue, 10:20–11:20
bellsoft.bsky.social
Testing #JavaFX often fails for common reasons: touching UI off the FX thread, racing the event queue, flaky pixel checks, Monocle misconfig in CI, FXML classloader traps.
@cat-edelveis.bsky.social explains the pitfalls and how to avoid them, with code:
dzone.com/articles/top...
Top 7 Mistakes When Testing JavaFX Applications
Testing JavaFX programs may seem non-trivial at first. This article describes the most common mistakes when testing desktop apps, their causes, and solutions.
dzone.com
bellsoft.bsky.social
Many teams still rely on Lombok, but few realize what it actually does under the hood. In this video, @cat-edelveis.bsky.social explains how Lombok rewrites your code and when it might be safer to move on: youtu.be/D-4mWspCz58
bellsoft.bsky.social
OpenJDK distributions offer a way out. They are TCK-verified and compatible with Oracle JDK, provide longer free update timelines, and offer support prices based on infrastructure size rather than employee count.
bellsoft.bsky.social
The outcome for enterprises: higher costs that grow with employee count, upgrade pressure, and sudden changes to Java SE products roadmap.
bellsoft.bsky.social
September 2025 brought another shift. Just a few days before JDK 25 release, Oracle announced that GraalVM for JDK 24 was the final GraalVM release licensed and supported as part of Oracle Java SE products.
bellsoft.bsky.social
For older versions, the deadlines are known. Free updates for Java 8 and 11 ended in 2019. Paid support for Oracle Java 11 ends in September 2026, and for Java 8 in December 2030.
bellsoft.bsky.social
In 2023, the pricing model shifted to the Java SE Universal Subscription. Instead of licensing per server, costs are now calculated by total employee count. This meant dramatic budget increases for many enterprises.
bellsoft.bsky.social
The NFTC license introduced with JDK 17 offers only three years of free updates per LTS release. That window closed for JDK 17 in September 2024. It will close for JDK 21 in September 2026. After that, you upgrade or pay.
bellsoft.bsky.social
In 2019, Oracle ended free updates for Java 8 used in production. Running a secure JDK now meant buying a subscription or switching vendors.
bellsoft.bsky.social
Oracle frequently changes the rules of Java licensing. Costs tied to the total number of employees, new schedule for free updates, GraalVM pulled out of Java SE. Here’s what’s changed in recent years and why many companies are moving to OpenJDK 🧵
bellsoft.bsky.social
#Java25 adds scoped values, a safer alternative to thread-local variables. Cleaner state sharing, less hidden leaks, perfect for virtual threads:
bellsoft.bsky.social
At #Dev2Next in Colorado Springs?
Tomorrow 2:15 PM, catch @asm0dey.site and Jonatan Ivanov on:
🔧 From Mystery to Mastery: Decoding the JVM with Observability Tools.

Real-world ways to debug CPU spikes, memory loss, and latency with observability that works.
bellsoft.bsky.social
Should you still use Lombok in 2025?
In this new video, @cat-edelveis.bsky.social explains how it rewrites your code, why it breaks with new JDKs, and when it might be time to move on: youtu.be/D-4mWspCz58
bellsoft.bsky.social
That’s just the surface. From testing to docs to brand new features, OpenJDK welcomes contributions of all sizes. Full guide (with a real API contribution example from our team): bell-sw.com/blog/how-to-...
A guide to contributing to Java SE
Learn about ways of contributing to OpenJDK and the process of integrating changes to the API.
bell-sw.com
bellsoft.bsky.social
📖 Docs and JEPs
Updating JavaDocs, writing guides, or explaining APIs is a contribution too.
And if you have a bigger idea? That’s where JEPs come in – the formal process behind features like Records, Virtual Threads, and Pattern Matching.
bellsoft.bsky.social
👀 Reviewing code
You don’t need committer rights to review changes. Feedback on clarity, performance, or test coverage is always welcome. Reviewing is also the best way to learn OpenJDK internals before proposing your own patch.