Because when you try to manage dependencies with Gradle on Android you realize that it could be worse. Much, much, worse. These are the languages and package m

Because when you try to manage dependencies with Gradle on Android you realize that it could be worse. Much, much, worse. These are the languages and package managers I have experience with: - JavaScript and npm - Python and pip/conda - Kotlin and Gradle - Scala and mill - Common Lisp and quicklisp - Racket and raco - Raku and zef - Lua and luarocks - Elixir and mix - Haxe and haxelib - Rust and cargo - Nim and nimble - OCaml and opam - Smalltalk and Monti/Meta-cello; also Visual Works parcel manager - and a few others Out of all these, cargo, opam, mix, and zef are the only ones that are mostly working as intended. They're still a pain, but they're predictable and honest about their limitations. Everything else is just bad, to the point where it's a waste of time to think about which is the biggest and which are a bit less of a clusterfuck. For some of these I had to resort to building a chroot env with a copy of my system inside to convince them to compile and link against correct libraries. If that's not a clusterfuck, I don't know what is... Unless you were lucky to see something better than "mainstream state of the art" solutions, you won't realize how bad it actually is. At that point you start inventing yarns or poetries, adding layers on top of layers to paper over simplistic, hardcoded assumptions made by original authors 20-30 years ago, and go into denial when someone tells you that's not going to fix anything.