I know it’s not monopoly now, but there’s always the risk of heading in that direction. Microsoft already controls LinkedIn, and Azure, which means it already has a great influence on the hiring as well as development process. Having a plugin registry will make people even more dependent on their services.
But you’re right, it’s better than 10 years ago, and there is still quite a bit of competition (I use GitLab myself ). Plus Git itself is decentralised so there’s no risk of losing the main code even if you have to switch away the rest for some reason.
Less on the philosophical side: I’m sure the feature would be very convenient for plugin developers. (Just as the “releases” feature is convenient for me: it’s one reason I still use GitHub as well as GitLab, because the latter doesn’t give special treatment to “release” tags and doesn’t let me upload such large files).
Also, I don’t know much about plugins beyond doing
npm install to get them: what were the issues with npmjs.org that you were referring to? Also, I sometimes see plugin installers download git repos anyway (not sure if it was
npm or something else): so perhaps the change isn’t as radical as it seems?