JVM build tools have to do much more than just dependency management because of how the JVM works (e.g. packaging resources). It's not really comparable.
It is literally creating zip file with jar extension and files inside of it. I’m pretty sure if they managed to figure out clusterfuck of Python, they can do the same for Java.
That's like saying "programming is just creating files with content".
Python is a purely interpreted language that runs in the context of your file system. Java code needs to be compiled and packaged, you have to write a manifest, you have to decide whether to include dependencies (fat jar) or not, or maybe you want to create a war (if you're stuck in the 2000s)... then what about maybe distributing the sources too?
Also, Maven works. Gradle works. Mill probably works too. The reason uv is a success is that everything Python had before was a broken mess. When people complain about JVM build tools, they come from a different position, not from one of "stuff is completely broken".
> Java code needs to be compiled and packaged, you have to write a manifest, you have to decide whether to include dependencies (fat jar) or not, or maybe you want to create a war (if you're stuck in the 2000s)... then what about maybe distributing the sources too?
I would probably be amazed at complexity of this, if I never touched Java in life.
The things you’re describing are literally a matter of a bash script to stitch together javac, jar and a couple of Unix tools.
Gradle is a monstrosity and abomination against the world. The only reason it exists is to give job to devex engineers and I’m willing to die on the hill. Maybe if it was rewritten in something faster and less memory hungry I’d be able to tolerate all this needless complexity, but until this piece of shit stops hogging all my memory and CPU time – its place is in the dumpster.
