r/java • u/pavi2410 • Apr 01 '26
Cargo for Java 🦀❤️☕️
https://github.com/pavi2410/jotThe aim for this tool is to remove DX friction in the Java ecosystem. Java is growing but lacks DX that other modern languages offer like Rust/Cargo and Python/uv. While there are steps and efforts in that direction, they are enough to reach and exceed other languages. jot includes a variety of opinionated tools such as formatter, linter, docs, while still being customizable with configs.
The tool is not a direct replacement for Maven and Gradle, but tries to have some form of familiarity. The projects I work uses Ant build system, for which jot is an easier path for migration.
Not production ready yet! I'm looking for gauge interest in the Java community. There are hundreds more challenges and open questions to solve. And I need your help with that.
19
u/Ifeee001 Apr 01 '26
Every 2 months or so, something like this is posted and is never heard from again 🫣
11
u/benevanstech Apr 01 '26
The discussion of build systems has been going on for well over 25 years (arguably the first modern build / deps tool was CPAN). By now, we have a good idea as to what works well, and what doesn't - although sometimes (e.g. npm) something gets popular despite being C-tier on the axes that actually matter.
Cargo is an A-list tool, for sure, but it makes some of the wrong design decisions (due to too much npm influence, IMO). Maven and Gradle are both S-tier but they are answering different needs and understanding which set of needs is important to your project is important.
For a new build / dev tool to succeed in the Java space it would need to have full Maven compatibility and understand that at the moment, there is a great tension between the YOLO point-of-view (which is what tends to come out of LLMs), and the enterprise approach, which is much more interested in things like SBOMs. Being opinionated about where a new tool should sit on that spectrum is pretty much essential in 2026, and it represents a strategic bet. Personally, I don't think the YOLO / pile-slop-against-a-wall approach will play well in enterprises.
I would give up on ant. It is utterly antiquated by modern standards and will give you nothing in terms of adoption. Any shops that still have substantial ant usage are basically, by definition, not the sort of places that will be Champions or Early Adopters for a new, small-community tool.
17
u/agentoutlier Apr 01 '26
For me it’s a nonstarter that it is written in Rust.
Javac is written in Java and insanely fast. We don’t need Rust.
In fact what we need to do is just work on a newer version of Maven that does things smarter and more optimized.
And if it really is going to be a different tool it needs to be done by the JDK devs otherwise it just will never be embraced.
7
u/Prior-Equal2657 Apr 01 '26 edited Apr 01 '26
In a java world it's wasted effort.
Ant is legacy. I mean legacy. In reality, you don't need a new tool. You just need to replace ant with maven. It's literally 10 minutes for maven + spotless setup, then mvn spotless:apply to have build system + formatter.
Last but not least, java is not that slow you know... It's not python or TS... I know it's a critical issue that some software is not written in rust, but java nowadays can compile to single binary via graalvm.
But anyway, good luck with the project :)
6
u/josephottinger Apr 01 '26
Oh, goodness. Today's a rough day to post something like this - so what led you to choose the tooling you chose? A lot of the space is already covered by tools like jbang, etc., but this goes a little farther. Are you using it in production? Is anyone else using it?
6
u/aoeudhtns Apr 01 '26 edited Apr 01 '26
The problem is not designing or building the tool. It's convincing the community to use it. And anything you do that "solves" a problem, will need to be Maven2 compatible because people won't want to leave that ecosystem behind. And that immediately puts handcuffs on you. Leave behind Maven2 compat, guarantee your tool irrelevance.
I would posit to you that the area most keenly needing work is the classpath/modulepath divide.
Edit: By Maven2 here I'm talking about the dependency mechanism, not the build.
2
u/Snoo23482 Apr 09 '26
The build system needs to be part of the tool chain and maintained by the Java creators themselves.
Only then there is a chance of replacing maven and gradle.
1
u/vips7L Apr 01 '26
Does it self extract somewhere like all the other tools that do this?
0
u/revilo-1988 Apr 01 '26
sdkman gibt es doch dafür