Kotlin kontra Java - Part 3 - Language for Interop

Thu, 07 May 2026 07:00:01 +0000

When you start a new project on the JVM, should you pick Java or Kotlin? Why not both?

You can use any Java library you want in Kotlin, you can even co-write your software in both languages (e.g. one team I work with writes their JUnit tests in Kotlin, their main code in Java) and migrate to Kotlin or back to Java over time. Kotlin is designed with Java interoperability in mind, because JetBrains wanted to migrate their IDEs (IntelliJ IDEA, WebStorm, etc.) incrementally to the language. But how does that work? What does Kotlin do, so that interop to this degree becomes possible?

Security in the Age of Java 25: New Language Tools for Safer Code

Tue, 30 Dec 2025 07:00:03 +0000

Security is more than just encryption - it’s also about how you write code. There are several Java security features that can help prevent logic bugs, misuse of types, and unexpected state mutations. Learn how sealed classes, pattern matching, and records can reinforce domain modeling, reduce null checks, and prevent injection-prone scenarios.

Introduction: Why Java security features Matters More Than Ever

Application security has never been a static field. Over the past two decades, the Java platform has evolved not just as a runtime for enterprise applications but as a trusted foundation for industries ranging from finance and healthcare to government systems. Security breaches, once attributed primarily to poor encryption or missing authentication, now more often stem from subtler flaws: unchecked input, leaky abstractions, and poorly modeled domain logic.

Immutability on JAVAPRO International

Kotlin kontra Java - Part 3 - Language for Interop

Security in the Age of Java 25: New Language Tools for Safer Code

Introduction: Why Java security features Matters More Than Ever