A large majority of people you’re chiding for not learning from others, don’t even realize those other things exist.
The car industry probably wouldn't be as big, if you had to learn a new tool for every new car.
The reason this is a problem is because web tech is constantly changing, to the point that so many of these projects end up in the scrap heap far faster than other tech. It causes problems with long term service due to compatibility issues with ever changing dependencies.
And sometimes it’s just resume building or intellectual curiosity itching.
There is something exciting about developers using a language in ways it was never designed. Then having the language change to support the changing ecosystem...
(as it happens 1.7 was released recently.)
Can you expand a bit more? Not sure what this means.
And the list goes on and on IMO. What's disappointing is that these were lessons learned a long time ago and now they're being re-learned.
I know.  and  have nothing to do with a package repository you can’t delete things from.
But anyways,  is at least a problem in many other package repositories.  would probably be a problem for many - given legal pressure (vendor your shit, that's the solution).  was a bug, not a design issue - no package management system is immune to bugs.
The one thing Java has is that it uses namespaces, which may help with  (but barely).  certainly has been a problem in PyPI.
Certainly all of this could happen to PyPI. We see it happen with js more, I think, because js happens to be extremely popular so there's a ton of packages for it and it's also much younger (especially node) than others.
He does have it in his slides.
Slide titled: "Regret: package.json", last 2 points:
> Ultimately I included NPM in the Node distribution, which much made it the defacto standard.
> It's unfortunate that there is a centralized (privately controlled even) repository for modules.
Just trying to clarify that he does actually talk about NPM and his regret about it.