18
JPlus - A fully Java-compatible superset language (github.com)
submitted 10 months ago* (last edited 10 months ago) by to c/programming@programming.dev
23 comments fedilink hide all child comments
 

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
[–] 2 points 10 months ago (7 children)

How does this post differ from this one? Why make two posts for the same thing?

  • permalink
  • fedilink
  • source
  • hideshow 7 child comments
    •
  • [–] [S] 1 point 10 months ago (6 children)

    As the title suggests, this page is an introduction to the project, while the other posts focus on how to use it.

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

    This is a distinction without a difference. Both introduce and explain how to use the project.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] [S] 0 points 10 months ago (3 children)

    Is this your first time here? The link in this post leads to the GitHub JPlus repository, while the other posts ultimately link to explanations on how to handle null safety using the JPlus IntelliJ plugin. Aside from the brief introduction, check out the additional links.

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

    Is this your first time here?

    Your account is brand new and you've already posted now three posts related to JPlus in this community in one day. Please tell me you're joking with this one.

    This post is a GitHub link to the project. Cool, I love seeing new projects, especially when the goal is to make it harder to write buggy code.

    The other post is an article that immediately links to the GitHub. The GitHub contains a link at the top to, what I can tell, the same exact article. Both the article and the GitHub README explain what JPlus is and how to use it.

    Why is this two posts when they contain the same information and link to each other directly at the top?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 0 points 10 months ago (1 child)

    First of all, thank you for your interest in the JPlus project. I also apologize if anything I said earlier came across as rude.

    The point I think was misunderstood is that, while the content of the posts is similar, the links they contain are different. To clarify once again, the link in this post directs to the JPlus GitHub repository, whereas the link in the post you mentioned points to the JPlus blog on Hashnode. Please check again.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 4 points 10 months ago

    You're aware you can just link to all relevant pages in a single post, right? You can add links to your description.

    programming.dev is a Lemmy instance, right? Then you should be able to use masked links via Markdown too. Like this: [text](link), it'll display as clickable text.

    What the person you're arguing with is annoyed by is that you're making a new post for every page you think is relevant. When you should be making one post that says all you want to say and links to all the pages you want to link to.

  • permalink
  • fedilink
  • source
  • parent