i didn’t create this post in the general programming community.

This is JADEx post. get out of hier.

This is JADEx post. get out of hier.

This is JADEx post. get out of hier.

By that logic, every object-oriented language is just Smalltalk diluted with something. Dilution isn’t degradation. Sometimes it’s just called adoption.

Thank you! I’ll keep working to make JADEx a compelling option for teams in exactly that situation. Your interest and any feedback along the way means a lot.

JADEx will be maintained for as long as I’m alive, so I suppose I’d better try to stick around as long as possible.

Seriously though, I’d love for more people to get involved and contribute to the project. The more contributors it has, the less that concern applies. If JADEx’s direction resonates with you, any contribution (whether it’s code, money, feedback, or just spreading the word) is genuinely appreciated.

JADEx is a solution designed to enhance null-safety in Java. Its key advantage is that existing Java developers can gain null-safety and final-by-default semantics without any learning curve. As a result, compared to migrating to Kotlin, JADEx offers a much more cost-effective way to significantly improve the stability of the legacy Java codebases that many companies continue to operate.

The key point about JADEx is that it’s not intended to compete with Kotlin or replace it.

Kotlin is a separate JVM language with its own ecosystem, compiler, and language model. Migrating a large legacy Java codebase to Kotlin is essentially a language migration project. Even though IntelliJ can automatically convert a lot of Java code, in practice teams still need to review the generated code, adapt APIs, update tooling, and spend time validating the behavior of the migrated system.

JADEx tries to address a different scenario: teams that must stay within the Java ecosystem but still want stronger null-safety guarantees.

Rather than introducing a new runtime or replacing the language, JADEx works as a source-level safety layer:

Java source → JADEx analysis & operators → null-safe Java source

The output is still ordinary, human-readable Java that compiles with the standard Java compiler and works with existing Java libraries and tooling.

Because of that, the adoption model is different from Kotlin. Instead of migrating the entire codebase, teams can apply JADEx gradually to specific parts of an existing Java project to strengthen null-safety.

Kotlin is a great choice for many projects, especially for new development. JADEx is mainly aimed at improving safety in large existing Java codebases where a language migration is not practical.

I’ll restructure the README so that the core idea of the project is easier to grasp and expand the Kotlin comparison section in the documentation, since it’s clearly one of the first questions people have when they see the project.

Thank you for your feedback.

I think there may be a bit of misunderstanding about what JADEx actually is.

JADEx is designed as a Java safety layer, not a new programming language. It behaves more like a tool that sits on top of Java and strengthens null-safety while keeping full compatibility with the existing Java ecosystem.

The workflow is essentially:

Java (input) -> JADEx tool -> null-safe Java (output)

In other words, developers still work within the Java ecosystem, and the final output is standard Java source code that can be compiled with the regular Java compiler.

The key idea is that existing Java code does not need to be rewritten. You can gradually apply JADEx to strengthen null-safety in legacy codebases without migrating the language itself.

Migrating a large legacy codebase to Kotlin, on the other hand, is closer to a language migration project. It typically requires substantial effort: rewriting parts of the codebase, updating tooling, and spending significant time validating and testing the migrated code.

Because of that, the cost and risk profile are very different.

JADEx aims to provide a lower-friction path to improve safety in existing Java systems, especially for teams that must remain in the Java ecosystem.

Kotlin is a great language and an excellent choice for many projects.

In fact, a very reasonable approach could be:

• strengthen existing legacy Java systems with JADEx
• write new components in Kotlin if the team prefers it

Those two approaches are not mutually exclusive and they simply solve different problems.

JADEx enhances Java with null-safety and readonly (final-by-default) semantics without requiring developers to switch languages. Existing Java developers can adopt these safety features with virtually no learning curve.

Compared to migrating to Kotlin, JADEx provides a significantly more cost-effective way to improve the reliability of large legacy Java codebases that many organizations still rely on.

JADEx enhances Java with null-safety and readonly (final-by-default) semantics without requiring developers to switch languages. Existing Java developers can adopt these safety features with virtually no learning curve.

Compared to migrating to Kotlin, JADEx provides a significantly more cost-effective way to improve the reliability of large legacy Java codebases that many organizations still rely on.

Thanks for your interest in JADEx. Please give it a try and feel free to share your feedback.

JADEx is a solution designed to enhance null-safety in Java. Its key advantage is that existing Java developers can gain null-safety and immutability without any learning curve. As a result, compared to migrating to Kotlin, JADEx offers a much more cost-effective way to significantly improve the stability of the legacy Java codebases that many companies continue to operate.

In addition, JADEx provides immutability, allowing developers to strengthen immutability without the verbose use of the final keyword.

We hope you continue to show great interest in JADEx. Thank you :)

In more detail, this feature was included as a preview in Java 21 and officially adopted in Java 25.

Let me correct a misunderstanding. JADEx was created as a Java superset language to strengthen Java’s insufficient null-related type system. In JADEx, Java’s reference types are assumed to be non-null by default, and through the nullability static analysis results provided by JADEx, developers can explicitly choose to mark types as nullable. Because of this, there is no problem using null-safe access operators and the Elvis operator.

To summarize:

• Java: All types are nullable; there is no non-null type. Therefore, Elvis operators and null-safe access operators cannot be used.
• JADEx: Both nullable and non-null types exist. Therefore, Elvis operators and null-safe access operators can be used.

I believe that if a company is a large corporation, it should provide financial support and take responsibility for large-scale bug reporting.

Unlike Java’s Optional, which is a library feature, JPlus provides null-safety at the language level. It allows developers to write code where null-safety is enforced consistently, without wrapping every value in an Optional. In that sense, JPlus brings the same kind of safety and clarity that Kotlin offers but keeps full compatibility with Java syntax and tooling.

What sort of financial situation are you in that 40$/month is sufficient?

I survive each day with just a bag of potato chips. Now, I’m reaching a point where even that is no longer possible. But rather than begging, I believe it’s right to offer my skills, bring value to others, and earn rewards in return. In the midst of a very difficult time, I came up with the idea for JPlus, and I’m deeply grateful for that. Without this project, I would have been in a much more troubled mental state. Through this project, I continue to dream of a hopeful future.