content: It's one reason I never include things like jquery via the Google CDN. I see a lot of people doing that and I think it's dumb. If you grow big enough, have your own varnish cache or buy a CDN subscription from someone. But at the same time, every app depends on other libraries. Look at your maven/sbt/gradle dependency files, your Rust toml files, Python's Pypy, or any package management system for any Linux distro... Now all these things have various levels of unpublishing ability .. which was the crux of the issue with node/npm. But don't kid yourself into thinking you can build something not dependent on other things that need to be pulled in for your builds. Unless you're writing some embedded C code, that's not happening.  Finally, this is a huge problem with npm. Fuck npm. For years every time I'd see a cool project and be like, "I want to try that out" and I'd clone it off github and than was like "aw fuck...node. Well npm install...yep..doesn't work...toss". I seriously didn't have time for that shit. It was rare npm built a god damned thing. The early atom editor ebuild overlays for Gentoo would constantly break without the ebuild changing!  These days, npm projects do seem to build/work. I don't know what changed. I haven't done any node development myself other than playing around with it. But from what I've done on it, it just looks dumb. Why are we building all this stuff...on Javascript? Async operations? On Javascript? That feels worse that Python and green threads.