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

481–490 of 588 posts

Re: NPM Is Joining GitHub

#481

Post by sah2ed »

nerdwaller wrote: post #459
K0nserv wrote: post #293

Earlier quoted context omitted.

That's a path but NPM already being a company with signficant VC investment would a transition to such a model workout with the existing stakeholders? Also NPM is quite a bit bigger than both the Ruby and Python library spaces.

> Also NPM is quite a bit bigger than both the Ruby and Python library spaces. I don’t know, so I have to ask, what’s the metric here?

Perhaps because Node code bases when deployed cause the package manager (npm) to consume more bandwidth in general than comparable Ruby or Python code bases due to higher dependence on third-party packages?

As at Oct. 2018, the top 12 npm packages [1] were already doing more than 0.5 billion downloads a month. Granted, popularity has waned for a few of those top packages due to deprecation or new language features, for instance.

EDIT:

NPM’s announcement about the acquisition [2] provides up-to-date numbers:

“Today, npm serves over 1.3 million packages to roughly 12 million developers, who download these things 75 billion times a month ...”

1: https://news.ycombinator.com/item?id=18343604

2: http://blog.npmjs.org/post/612764866888007680/next-phase-mon...

Re: NPM Is Joining GitHub

#482

Post by nl »

hnra wrote: post #477
nl wrote: post #448

Earlier quoted context omitted.

PyPy runs on donated infrastructure that costs over 800K/month in hosting costs[1]. Not many non-commercial entities can afford that. [1] https://twitter.com/dstufft/status/1236331765846990848

PyPI, not PyPy. For those confused over how PyPy could cost that much.

Yes you are correct of course - my mistyping!

Re: NPM Is Joining GitHub

#483

Post by nl »

pjmlp wrote: post #474
nl wrote: post #441

Earlier quoted context omitted.

I switched from Atom to VSCode well before the acquisition, and I personally know many others that did too. What need does Atom fill that VSCode doesn't?

Making use of idle cores.

Harsh, but true...

Re: NPM Is Joining GitHub

#484

Post by slightwinder »

peglasaurus wrote: post #457
girvo wrote: post #425

Earlier quoted context omitted.

They’re likely not supposed to be commenting on things like this as an active employee of the company in question.

Freedom of speech isn’t freedom from consequences, as is often said.

If there are consequences for your speech, then it's not free.

Re: NPM Is Joining GitHub

#485

Post by cool-RR »

throwaway78359 wrote: post #232

Microsoftie here — throwaway for obvious reasons. Microsoft doesn’t do everything right but the GitHub acquisition has honestly gone better than I ever expected. Rather than forcing GitHub to adopt Microsoft centric policies, Microsoft has adopted more GitHub stuff, especially from a product POV. GitHub still runs as a separate company (different logins and health care and hiring systems) with its own policies and po…

GitHub is still a good choice, but working with their more recent APIs, like GitHub Actions, I feel Microsoft's touch. They're slowly changing for the worst.

Re: NPM Is Joining GitHub

#486

Post by robertlagrant »

oorza wrote: post #356
Spivak wrote: post #239

Earlier quoted context omitted.

I think the honest truth is that a lot of developers see Safari similarly to IE because Firefox and Chrome are quick to jump on and ship new features and "if only Safari kept up" they could be used "everywhere". Combined with the fact that iOS is large enough that you can't just drop Safari support and tell them to use Chrome. It's a weird world where webdevs apparently ideally just want everyone on the 6 second old…

You're right, IE6 was amazing at the time. It made a ton of things possible that previously hadn't been, and the standards bodies were lagging behind it. Had MS actually kept updating IE6 and kept it ahead of the standards, the standards would never have mattered, and we'd never have developed this sick taste for IE. No one hated that they had a monopoly, we hated that they had a stagnant monopoly.

Your comment just triggered the box model. Which is what I call my flashbacks about when hasLayout was true or not.

Re: NPM Is Joining GitHub

#487

Post by slightwinder »

lewisl9029 wrote: post #449
chipotle_coyote wrote: post #440

Earlier quoted context omitted.

Counter thesis: what "killed" Atom is the balance of user enthusiasm quickly shifting to VSCode. Well before the acquisition was even announced, VSCode started grabbing developer mindshare real, real fast. I remember being an Atom user who resisted that tide for a while, but it became pretty clear that VSCode was taking off like a rocket and Atom, well, wasn't. If commit activity graphs are really a meaningful measur…

It would be delusional of me to claim that VSCode wasn't already winning in terms of mindshare by a large margin when the acquisition happened. That's not what I'm claiming here. Atom still had a healthy number of active contributors (presumably most of them were from GitHub) making improvements to the product on a daily basis to make it a perfectly viable tool for the people who chose to use it (and despite the much…

How many of those github-people were officialy working on atom and how many were just random githuber who supported company-focus and followed social pressure?

It's quite possible that this was just a random side-effect from a shift in focus, instead of a planned sabotage.

Re: NPM Is Joining GitHub

#488

Post by popinman322 »

slightwinder wrote: post #484
peglasaurus wrote: post #457

Earlier quoted context omitted.

Freedom of speech isn’t freedom from consequences, as is often said.

If there are consequences for your speech, then it's not free.

You're conflating definitions of the word free.

Free in "freedom of speech" is the ability to say anything you want.

Your choice of free means cost.

So you're free to speak, but the speech itself isn't free.

Re: NPM Is Joining GitHub

#489

Post by robocat »

Galanwe wrote: post #479
throwaway78359 wrote: post #232

Microsoftie here — throwaway for obvious reasons. Microsoft doesn’t do everything right but the GitHub acquisition has honestly gone better than I ever expected. Rather than forcing GitHub to adopt Microsoft centric policies, Microsoft has adopted more GitHub stuff, especially from a product POV. GitHub still runs as a separate company (different logins and health care and hiring systems) with its own policies and po…

> Microsoft doesn’t do everything right but the GitHub acquisition has honestly gone better than I ever expected. Rather than forcing GitHub to adopt Microsoft centric policies, Microsoft has adopted more GitHub stuff, especially from a product POV. GitHub still runs as a separate company (different logins and health care and hiring systems) with its own policies and point of view. That's what we said about the Skype…

> That's what we said about the Skype acquisition too.

“On 10 May 2011, Microsoft Corporation acquired Skype Communications, S. à r.l for US$8.5 billion”

I think Microsoft has changed significantly in the last decade.

I’m quietly hopeful the npm acquisition will go well for us (although I still hold some serious grudges about Microsoft’s past behaviour).

Re: NPM Is Joining GitHub

#490

Post by slightwinder »

popinman322 wrote: post #488
slightwinder wrote: post #484

Earlier quoted context omitted.

If there are consequences for your speech, then it's not free.

You're conflating definitions of the word free. Free in "freedom of speech" is the ability to say anything you want. Your choice of free means cost. So you're free to speak, but the speech itself isn't free.

Your definition makes zero sense. Unless you are physical unable to speak, you are always "free" to speak, saying whatever you want.

Freedom of speech is by definition exactly this: free of consequences.

Post reply on HN