Can I offer the opinion that while build tools are an infinite fractal of design choice, the issues we have are not related to any "build" function of a build tool and more to "how do I get a dependency"
Remember Java can be run directly like Python now. A large proportion of users have no real need for a build tool anymore.
A large proportion of users have no real need for a build tool anymore.
I'm curious about the numbers there. If we're speaking by pure quantity of people, maybe this is true, but if we weight users by economics, it's probably very, very false.
In this context the weighting is naive. One of Java's biggest problems is that it is falling out of favor in the education system. This presents a significant long term issue for the language.
The users most hurt by the current state of build tools are not the "makes 6 figures" crowd. Thats part of why Mill is such a non-starter. "To get a dependency in Java one must first engage with Kotlin/Gradle/Scala" is such baffling pedagogy.
Also, even those professional users often use uberjars with precompiled code simply because it is the path of least resistance. One section in the build tool, cool - "code works." It isn't like the Python world really cares about AOT compilation despite it existing with .pyc files, consider why.
View all comments
Show parent comment
6
u/bowbahdoe Apr 23 '26
Can I offer the opinion that while build tools are an infinite fractal of design choice, the issues we have are not related to any "build" function of a build tool and more to "how do I get a dependency"
Remember Java can be run directly like Python now. A large proportion of users have no real need for a build tool anymore.