3 ms·
As someone else alluded to, I think the problem stems more from the fact that major official libraries are glued together using a lot of dependencies that aren’
by twodave 8y ago
As someone else alluded to, I think the problem stems more from the fact that major official libraries are glued together using a lot of dependencies that aren’t necessarily trustworthy. This doesn’t happen nearly as much in the other ecosystems (at least none that I have seen). In Android dev, for instance, you often will see the official Google support binaries as dependencies but nothing else. In .NET you’ll often see Newtonsoft’s JSON serializer but very few non-Microsoft third party dependencies.
- bunderbunder 8y agoIt does to a lesser, but still worrisome, extent in Java. I think it's precisely because it lacks a good committed (commercial) owner like Android and .NET have. I could see it going from bad to worse in the future, as Oracle continues to jettison responsibility for bits of the ecosystem.
- bradleyjg 8y agoI think it’s healthy to have an ecosystem of large, well vetted, third party libraries maintained by long-standing organizations like Google (guava), Apache (commons, hadoop), or Pivotal/Dell (Spring).
- pjmlp 8y agoThe early decade of Java open source was mostly driven by the Apache Foundation