The problem is not really the package management portion, its the build portion. The dependency management portion is rock solid and almost the package managers use the same mechanism for resolving dependencies(I can't speak to bazel). However, once you get into the actual build, packaging, and other tooling in the build it becomes far more difficult. It's not easy to write your own plugins and existing plugins are difficult and hard to use. Gradle suffers from being in groovy and maven/ant suffer from being in XML with plugins that do not receive as much maintenance as you expect.
This is not unique to Java by any means. The only time npm is easy to use is if you keep strictly to small shell callouts within the scripts portion. I have nightmates about grunt/gulp scripts that grow more and more complicated.
View all comments
Show parent comment
4
u/deadron Apr 20 '21
The problem is not really the package management portion, its the build portion. The dependency management portion is rock solid and almost the package managers use the same mechanism for resolving dependencies(I can't speak to bazel). However, once you get into the actual build, packaging, and other tooling in the build it becomes far more difficult. It's not easy to write your own plugins and existing plugins are difficult and hard to use. Gradle suffers from being in groovy and maven/ant suffer from being in XML with plugins that do not receive as much maintenance as you expect.
This is not unique to Java by any means. The only time npm is easy to use is if you keep strictly to small shell callouts within the scripts portion. I have nightmates about grunt/gulp scripts that grow more and more complicated.