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

71–80 of 588 posts

Re: NPM Is Joining GitHub

#71

Post by tylerchilds »

fxtentacle wrote: post #47
whoisjuan wrote: post #39

Earlier quoted context omitted.

I mean. It's a subsidiary. I understand your sentiment but mentioning Microsoft would be like signaling that GitHub doesn't have any autonomy which is quite the contrary to what Microsoft said when buying it. So don't expect sudden sincerity on this. There's a reason why they haven't added Microsoft branding to areas like the footer.

... and everyone knows that big corporations always speak purely from their open heart when they sign large acquisition deals.

well now I do ;)

Re: NPM Is Joining GitHub

#73

Post by Jaxkr »

mythz wrote: post #66

Just like GitHub this is a cloud play to make Azure more appealing by meeting developers where they're at, increase dev mindshare/reach, hosting their packages, CI Scripts/Actions then making it seamless to deploy to Azure. Smart, have no idea where AWS or GCP's control team are at when these strategic plays are going down.

I honestly think that Google cloud platform will be shut down within a couple years. It seems like it’s losing the war very badly.

Re: NPM Is Joining GitHub

#74

Post by Normal_gaussian »

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.

yarn v1+ or yarn v2/berry?

Switching to berry has been a huge PITA over here, but I don't want to give up workspaces

Re: NPM Is Joining GitHub

#75

Post by madeofpalk »

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.

I suspect you're still using the npm repository though? That's the actual 'valuable' thing that NPM (the company) makes.

Re: NPM Is Joining GitHub

#76

Post by sitkack »

batmansmk wrote: post #7

VsCode, Typescript, Github, NPM. And Microsoft doesn't even have to maintain the main runtime, Google does. What a clever strategy!

They could fork it, the core of the runtimework is moving to WebAssembly anyway which is a much more tractable problem. Sure this is a boatload of JS work to do at the interface boundary but the amount of hard compiler and jit work that needs to be focused on by main runtime is much lower.

Someone at MS knows strategic and tactics. When MS and Windows bootstrap themselves into the cloud, they will have some software to land on.

Re: NPM Is Joining GitHub

#77

Post by joshiefishbein »

ezekg wrote: post #64

Sorry, but npm burned me too many times. It is (was?) the worst package manager I've ever used. Not a fan of npm the company either. I'm sticking with yarn.

Yarn is majorly only a CLI. It still uses NPM as the source for most packages.

The product Github is probably most interested in is NPM as a repository for packages, not its CLI.

Re: NPM Is Joining GitHub

#78

Post by nathcd »

cortesoft wrote: post #63
nathcd wrote: post #44

Sometimes I wonder what the business world (and the internet) would be like if mergers and acquisitions weren't allowed. Like, if businesses had to be sustainable or they'd just die, rather than capturing a whole market while eating VC money, maybe we'd all be better off? All of the really embarrassing stuff coming out of SV would just go away? Just Pinboards and Sourcehuts and Mastodons ruling the web? I'm capitalis…

What would happen to all the tech, equipment, and employees after the company goes out of business? We have to burn it? If we did that, it would be a crazy waste of resources. The alternative is to let another company buy the stuff... and if a company buys the failed company's tech, equipment, and hires their staff... that is basically the same as buying the company.

I mean, what would normally happen is employees look for new jobs, equipment is sold, and tech is thrown away (or open sourced in rare cases). Doesn't this already happen all the time?

Re: NPM Is Joining GitHub

#79

Post by rtsao »

I hope this doesn't alter the current GitHub npm package registry policy where all packages must be published under a scope corresponding to name of the owning GitHub user/org. The resulting increased transparency and clarity of ownership will be great for the JS ecosystem.

The existing npm ownership model is markedly less clear and has led to several problems, including the transfer of package publishing rights to bad actors without anyone being aware. On the whole, npm accounts and orgs were always just an unnecessary abstraction that obscured the actual provenance of software, of which GitHub is the de facto source.

Re: NPM Is Joining GitHub

#80

Post by FooBarWidget »

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…

Microsoft is aware of their reputation. So much that they even have a policy of not allowing Microsoft+Github co-brand promotions. They want the Github brand to stay strong instead of being diluted into some mix of Github and Microsoft.
Post reply on HN