Skip Navigation

User banner

JADEx

@ justicecoder @programming.dev

Posts
14
Comments
48
Joined
9 mo. ago

  • Deleted

    Permanently Deleted

    Jump

  • This is JADEx post. get out of hier.

  • Deleted

    Permanently Deleted

    Jump

  • This is JADEx post. get out of hier.

  • Deleted

    Permanently Deleted

    Jump

  • This is JADEx post. get out of hier.

  • Deleted

    Permanently Deleted

    Jump

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

  • Deleted

    Permanently Deleted

    Jump

  • 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.

  • Deleted

    Permanently Deleted

    Jump

  • 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.

  • What if Java had Kotlin-style null-safety without migrating your Spring Boot project to Kotlin?

    Jump

  • 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.

  • Programming @programming.dev
    JADEx @programming.dev

    What if Java had Kotlin-style null-safety without migrating your Spring Boot project to Kotlin?

    github.com /nieuwmijnleven/JADEx
  • Programming @programming.dev
    JADEx @programming.dev

    JADEx v0.59: Gradle plugin support added - bring null-safety and final-by-default into your build pipeline

    github.com /nieuwmijnleven/JADEx

  • Safer Java Without Rewriting Java: Meet JADEx

    Jump

  • 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.

  • Safer Java Without Rewriting Java: Meet JADEx

    Jump

  • 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.

  • Safer Java Without Rewriting Java: Meet JADEx

    Jump

  • 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.

  • Safer Java Without Rewriting Java: Meet JADEx

    Jump

  • 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.

  • Opensource @programming.dev
    JADEx @programming.dev

    Safer Java Without Rewriting Java: Meet JADEx

    github.com /nieuwmijnleven/JADEx

  • JADEx Update v0.49: Improved IntelliJ Plugin Stability and Responsiveness

    Jump

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

  • Programming @programming.dev
    JADEx @programming.dev

    JADEx Update v0.49: Improved IntelliJ Plugin Stability and Responsiveness

    github.com /nieuwmijnleven/JADEx
  • Opensource @programming.dev
    JADEx @programming.dev

    JADEx Update (v0.42): Readonly Replaces Immutability Based on Community Feedback

    github.com /nieuwmijnleven/JADEx/releases/tag/v0.42
  • Programming @programming.dev
    JADEx @programming.dev

    JADEx Update (v0.42): Readonly Replaces Immutability Based on Community Feedback

    github.com /nieuwmijnleven/JADEx/releases/tag/v0.42

  • JADEx v0.41: Introducing Immutability for Safer Java Code

    Jump

  • 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.

  • Opensource @programming.dev
    JADEx @programming.dev

    JADEx v0.41: Introducing Immutability for Safer Java Code

    github.com /nieuwmijnleven/JADEx
  • Programming @programming.dev
    JADEx @programming.dev

    JADEx v0.41: Introducing Immutability for Safer Java Code

    github.com /nieuwmijnleven/JADEx

  • JADEx: A Practical Null-Safety Solution for Java

    Jump

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

  • Python vs. Java

    Jump

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

  • JADEx: A Practical Null-Safety Solution for Java

    Jump

  • 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.
  • Opensource @programming.dev
    JADEx @programming.dev

    JADEx: A Practical Null-Safety Solution for Java

    github.com /nieuwmijnleven/JADEx
  • Programming @programming.dev
    JADEx @programming.dev

    JADEx: A Practical Null-Safety Solution for Java

    github.com /nieuwmijnleven/JADEx

  • FFmpeg to Google: Fund Us or Stop Sending Bugs

    Jump

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

  • [Sponsorship Request] JPlus: A New Tool for Java Developers, Small Support Needed

    Jump

  • 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.

  • Deleted

    Seeking Opinions on Default Value Support in Named Parameter Feature

    Jump

  • Okay. You must realize it is weird to use the term “development team” to describe a one person side project. Also, are you willing to disclose to what extent and which models were used to create this project?

    JPlus is an open-source project. Anyone can review the implementation details on GitHub: https://github.com/nieuwmijnleven/JPlus

  • Opensource @programming.dev
    JADEx @programming.dev
    Sponsorship Request

    JPlus: A New Tool for Java Developers, Small Support Needed

    github.com /nieuwmijnleven/JPlus
  • Opensource @programming.dev
    JADEx @programming.dev

    A New Boilerplate Code Generation with JPlus

    jplus.hashnode.dev /tired-of-lombok-try-apply-in-jplus-with-built-in-boilerplate-elimination
  • Programming @programming.dev
    JADEx @programming.dev

    JPlus - A fully Java-compatible superset language

    github.com /nieuwmijnleven/JPlus
  • Programming @programming.dev
    JADEx @programming.dev

    Make Your Java Code Null-Safe Without Rewriting

    jplus.hashnode.dev /writing-java-code-safely-and-smartly-with-null-safety-using-jplus