I understand some folks trepidation but where was npm going anyway?
NPM Is Joining GitHub
31–40 of 588 posts
Re: NPM Is Joining GitHub
#32"Github acquires npm" would be a better title IMO.
Today we've announced that we've signed an agreement to acquire NPM but we technically have not acquired them yet (referred to as "closed"). NPM is still their own company for now and that's why the language is future tense.
Re: NPM Is Joining GitHub
#33Is this a too big to fail kind of charity acquisition?
no, this is microsoft "embracing" (buying control of) a huge point of centralization in a software distribution ecosystem, positioning them to have greater power over a huge number of developers.
Re: NPM Is Joining GitHub
#34"Github acquires npm" would be a better title IMO.
Re: NPM Is Joining GitHub
#35I'll be switching from Github to other providers for my own projects, and use a different editor soon (using vscode now).
Re: NPM Is Joining GitHub
#36Re: NPM Is Joining GitHub
#37Re: NPM Is Joining GitHub
#38Embrace, extend, extinguish.
Re: NPM Is Joining GitHub
#39I'm surprised there's not a single mention of "Microsoft" in this or the npm announcement [1], given the old-evil-history of Microsoft and the new-nice Microsoft we have today. I would expect that there was at least a mention, considering the reason that most modules in npm are still in ES5 is exactly because of the monopolistic practices that Microsoft followed back in the day which makes Internet Explorer still rel…
Re: NPM Is Joining GitHub
#40"Github acquires npm" would be a better title IMO.