Ridiculously low-quality documentation, a build and development system that puts the local Rube Goldberg competition winner to shame, constant churn, total deafness or willful ignoring of wishes of dev ... and so on have nothing to do with what happened 20 years ago.
It's the classic "I would like to serve 5 terabytes"[0] Google problem.
(Their engineering culture reeks of this. See the tools they have released. Angular, Bazel, Go, Kubernetes, etc. The last one escaped the usual decline of incompetence because the community showed up.
Go has GOPATH. Even in a language designed for "simplicity" initially getting it set up had this roadblock.)
And no doubt the roots of the problem are manifold, but it seems all stemming from ongoing management incompetence (creation of shareholder value[1] maaaybe excluded, though I am very curious what kind of inane metrics the Android SDK team is whipped to chase).
It's the classic "I would like to serve 5 terabytes"[0] Google problem.
(Their engineering culture reeks of this. See the tools they have released. Angular, Bazel, Go, Kubernetes, etc. The last one escaped the usual decline of incompetence because the community showed up.
Go has GOPATH. Even in a language designed for "simplicity" initially getting it set up had this roadblock.)
And no doubt the roots of the problem are manifold, but it seems all stemming from ongoing management incompetence (creation of shareholder value[1] maaaybe excluded, though I am very curious what kind of inane metrics the Android SDK team is whipped to chase).
[0] https://www.youtube.com/watch?v=3t6L-FlfeaI&t=0s
[1] https://www.wheresyoured.at/the-men-who-killed-google/