> See JavaScript/TypeScript, Python, or C/C++. I feel like you've picked the 3 worst ecosystems as an example. Java has a wonderful ecosystem. You can use Mav

> See JavaScript/TypeScript, Python, or C/C++. I feel like you've picked the 3 worst ecosystems as an example. Java has a wonderful ecosystem. You can use Maven/Gradle/Bazel as a dependency manager/build tool. All support the Maven repository format. Packages are published as jars and easily consumed. Of course you can still end up in dependency hell and you should take steps to mitigate those issues, but I'm quite happy with it. > As a result, we keep building new variants and features, until we end up with <script>, require(), import, npm, yarn, pnpm, (py)?(v|virtual|pip)?env, (ana)?conda, easy_install, eggs and wheels ... IMO the problem here is that there isn't a monopoly and its easy to swap in a replacement. JavaScript/Python developers are happy (or willing) to try something new, so new alternatives are created. Convincing a Java developer to try a new build system is difficult, so changes are made to existing systems rather than creating new ones. Go and Rust are two other systems that work well and are (almost?) universally adopted. They come with the language and there is little reason to look around.