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.

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.