4
JADEx: A Practical Null-Safety Solution for Java (github.com)
submitted 7 months ago by to c/programming@programming.dev
8 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] -2 points 7 months ago (6 children)

There are many valid practical reasons to avoid Kotlin in certain circumstances (not the least of which being Russian ties). More tools for Java isn't necessarily a bad thing. However I don't really think it works. It reminds me of this blog post: https://www.javacodegeeks.com/2017/02/elvis-not-visit-java.html which I think accurately reflects many of my thoughts about null-safety in Java.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 3 points 7 months ago (2 children)

    What Russian ties? JetBrains is a Czech company, with very little income from Russia. They suspended sales in Russia and Belarus in 2022. https://www.jetbrains.com/lp/annualreport-2022/

    And please do list the practical reasons for avoiding Kotlin.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 7 months ago (1 child)

    Just the historical Russian ties, which is enough for some people/organizations to avoid them. The biggest practical reason is the dependence on tooling. Kotlin is a great language, but loses a lot of its allure when you can't use an IDE for whatever reason. It makes sense, given that its developed by a company whose main product is IDEs; but it can still be an issue in some circumstances.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 7 months ago

    What makes kotlin different from any other language in that regard? It’s better to use an IDE that supports the language than a plain text editor that has no tooling. That’s just a fact of programming.

  • permalink
  • fedilink
  • source
  • parent
  • [–] [S] 2 points 7 months ago (2 children)

    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.
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •