this post was submitted on 06 Nov 2025
17 points (79.3% liked)

Programming

23894 readers
260 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
 

JPlus is fully compatible with Java, offering modern language features like null safety, boilerplate code generation and other modern language features to reduce developer burden and maximize productivity.

Notably, there is currently no ‘superset’ language that keeps Java syntax almost intact while extending the language with features like null checks at the language level. JPlus aims to fill this gap, providing a language that existing Java developers can naturally learn and adopt.

you are viewing a single comment's thread
view the rest of the comments
[–] Pamasich@kbin.earth 9 points 1 month ago (11 children)

Notably, there is currently no ‘superset’ language that keeps Java syntax almost intact

There's groovy iirc.

[–] justicecoder@programming.dev 2 points 1 month ago (9 children)

Notably, there is currently no ‘superset’ language that keeps Java syntax almost intact

There’s groovy iirc.

Groovy is highly compatible with Java and most Java code runs in Groovy without changes. However, it’s not 100% identical. Groovy introduces dynamic typing, additional syntax, and runtime behaviors that can differ from Java. JPlus, on the other hand, aims to keep Java syntax almost intact while adding null-safety and boilerplate code generation making it easier to apply to existing Java projects without rewriting code

[–] Pamasich@kbin.earth 10 points 1 month ago (8 children)

This isn't an accusation, but was this comment written with AI? There's a glaring logical error here which I think a human would catch easily, but an LLM (which is just a natural language generator, not a logic processor) could possibly overlook.

Specifically, your arguments don't really make a lot of sense. They're also not targeted at my claim. It reads more like a defense of JPlus. To which I want to clarify, I merely took issue with the specific claim I quoted, I wasn't trying to say there's no point to JPlus. There's no need to defend JPlus in general. So I'm going to dismiss runtime behaviors since that has nothing to do with the syntax.

Groovy introduces dynamic typing

Java has dynamic typing already. Groovy introduced it first, but it's not a Groovy exclusive feature anymore. It's also optional.

additional syntax

There being additional syntax doesn't matter if it's optional. We're talking here about whether Java code works in Groovy/JPlus, and it does. Not the other way around. At least that's what I understood.

JPlus also adds the nullsafe and elvis operators, so it also adds additional syntax and JPlus code won't work when compiled with Java directly.

Groovy is highly compatible with Java and most Java code runs in Groovy without changes. However, it’s not 100% identical.

JPlus also doesn't guarantee being 100% identical. It says "mostly" the same.


Basically, none of the arguments really compare the two in the context given. The runtime behavior is the only real difference listed here, but that's irrelevant in the context of them being supersets.

[–] expr@programming.dev 3 points 1 month ago (1 children)
[–] Hammerheart@programming.dev 1 points 1 month ago

I'm pretty confident it was written by an LLM.

load more comments (6 replies)
load more comments (6 replies)
load more comments (7 replies)