Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

NPM Is Joining GitHub

github.blog

Post reply on HN
Print view View original

81–90 of 588 posts

Re: NPM Is Joining GitHub

#81

Post by pseudorandomguy »

franciscop wrote: post #26

I'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…

My fear might probably be unfounded, but NPM is an integral part of the JS ecosystem. And given MicroSoft has .NET Core, I have a strange feeling that they'll concentrate on npm less.

Re: NPM Is Joining GitHub

#82

Post by SahAssar »

hinkley wrote: post #21
sandov wrote: post #2

"Github acquires npm" would be a better title IMO.

I am glad that the npm team will finally have some adult supervision. Meanwhile, I almost have my team switched to yarn.

NPM is a lot more than the CLI. Even if you use yarn as the CLI you are still using npm for hosting and all the other parts that don't run on your computer. You can run your own npm repo, but hardly anyone does for all their dependencies (not talking about just caching here).

I'd wager most people who use yarn even installed it via the npm CLI.

Re: NPM Is Joining GitHub

#83

Post by fredsted »

banachtarski wrote: post #48
franciscop wrote: post #26

I'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…

I installed Windows Subsystem for Linux 2 on an older machine just now. The MSFT of today is definitely a far cry from the MSFT of yesteryear. Such a thing would have been unheard of 15 years ago.

Embrace, extend, extinguish?

Re: NPM Is Joining GitHub

#84

Post by clarkbw »

cmckn wrote: post #46
clarkbw wrote: post #11

Earlier quoted context omitted.

Part of GitHub (I work at GitHub and lead the Packages team)

How does this acquisition relate to Package's support of npm artifacts? Or, I guess, how will Package's npm support change after this?

The post covers this.

> Later this year, we will enable npm’s paying customers to move their private npm packages to GitHub Packages—allowing npm to exclusively focus on being a great public registry for JavaScript.

Packages will continue to develop its npm registry. We have a lot of work to do in securing the software supply chain.

Re: NPM Is Joining GitHub

#85

Post by cycloptic »

yjftsjthsd-h wrote: post #50
cycloptic wrote: post #41

Earlier quoted context omitted.

It was already consolidated. The vast majority of public npm packages are already hosted on Github. The dependency on them has been there since the beginning.

I would expect that moving git repos is easier than replacing NPM?

It is, but who is doing that? The users of NPM all are choosing to stay on Github.

Re: NPM Is Joining GitHub

#86

Post by bjt2n3904 »

You know, my initial reaction was... oh no, the toxic people who run NPM and Node.js[1][2] are going to infect GitHub.

But then I read that other front page article about the guy that got mysteriously "flagged", and the invasive questions he was asked. Maybe Github is already too far gone.

Maybe it should be... please, bundle all the toxic people together in one spot, and let it all come crashing to the ground. I've had serious reservations about using Node.js in a product I've been tasked to work on, for the reasons I listed below. It'd be great if they just... ceased to exist.

1 - left-pad incedent

2 - The Ayo fork drama

Re: NPM Is Joining GitHub

#87

Post by mythz »

bepotts wrote: post #54
mythz wrote: post #42

Earlier quoted context omitted.

They should get props for TypeScript & VSCode.

They do and I will give them props for that. But no company should have as much control over open source that Microsoft does.

They should & deserve to have full control over everything they've created.

You can blame AWS/GCP for letting GitHub & npm be acquired, how many years were they on the open market?

Most of the $$$ in OSS is being funneled towards rent-seeking major cloud providers that are hosting OSS software, whom should all have blank checks with the money they've reaped so far, but seems only Microsoft has the strategic savvy to focus on acquiring the obvious targets for increasing dev mindshare. I don't fault them for their M&A's, it's just good business.

Re: NPM Is Joining GitHub

#89

Post by reaperducer »

franciscop wrote: post #26

I'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…

I'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.

Maybe Microsoft's reputation is exactly the reason why it was left out of this announcement.

Sometimes a brand is so tarnished that the owner tries to hide it from the people who hate it. (For example, Comcast → Xfinity. I expect Monsanto to go the same way and become Bayer.)

Post reply on HN