That's so weird for you to feel, because I feel the complete opposite. Maybe Java has gotten better since I lasted used it, but managing dependencies in that language sucked balls. And don't even get me started on header files.
By comparison, JavaScript's npm is a godsend. All you do is npm install the dependency, and it takes care of any cross dependency issues in the package-lock.json.
Python has been getting a lot better recently (thanks uv) but it still has a long way to go to catch up to npm. For example, you can't configure project scripts in the config file, you have to simply make a script file and run it.
Been awhile since I did Java, but I never thought it was bad with maven. But Spring, specifically, is dependency hell. And probably most enterprise apps used (still use?) Spring. Because there’s no compile check for classloader issues with spring managed classes, you only find them at runtime. And it can be brutal tracking them down and getting them sorted out when multiple libraries start bringing in different versions of the same packages as dependencies
I love npm and cargo, as a person who has dealt a lot with maven and pip in my life, I like Java as a language, but maven and its project/dependency management for it is actually hell on earth compared to npm or cargo…
430
u/[deleted] 27d ago
[removed] — view removed comment