Live data from Hacker News

NPM Is Joining GitHub

github.blog

431–440 of 588 posts

Re: NPM Is Joining GitHub

#431

Earlier quoted context omitted.

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

> yarn v2/berry? I had still been following 1.x Looking at https://yarnpkg.com/advanced/migration : T-T We have so many little modules from different teams, or even borderline abandonware, that it would take ages to make these changes, and 'yarn node'?? Just... no. How is that ever gonna work consistently with node_modules/.bin? At this point my choices are, start contributing to yarn and npm development, or get my a…

Yeah, yarnv2 is a BIG change and one that came out without much noise. There is no node_modules now by default. Pnp is forced (which was released in yarn as an experiment back in 2018 without much adoption).

I have been wondering the same thing. I left node for 8 months and I come back to see a lot of things have been abandoned in favor of yet another wheel implemented a bit differently. I wish changes were more visible and subtle. Rewriting seems like a plaque to js ecosystem except no one rewrites some really old unmaintained dependency we have hidden in every new shiny project.

Re: NPM Is Joining GitHub

#432
post #406

Earlier quoted context omitted.

I guess every person who was put in a cage near the border of the US was a huge danger. https://www.aclu.org/issues/immigrants-rights/ice-and-border...

To keep this as straightforward as possible: Illegal immigration is a crime and is enforced just like any other. Committing crime can mean incarceration, which many US citizens face everyday. It has nothing to do with being a "danger", but when you don't have permission to even be in the country then there's no bail or other release possible. Also detainment centers are not cages but fenced areas with free movement i…

Almost every word of this is a lie, misleading or poor framing.

Re: NPM Is Joining GitHub

#433

Earlier quoted context omitted.

I think the poster was saying that .NET has a dev strategy, but other projects don't. > Microsoft can’t even put coherent dev strategy outside of .NET on Azure

You don't need Azure to use any part of .NET - and VSCode, Github, etc., stretch beyond both.

That’s not what was said either.

They said that .NET and Azure, two separate things, are very well managed. OP did not imply any correlation between the two of them.

Re: NPM Is Joining GitHub

#434
post #394

Earlier quoted context omitted.

I did search, didn't find it quickly. Could you share some sources of the negative impact? (I'm legitimately curious as my use of GitHub hasn't led me to notice any change.)

I found two pretty damn quickly. They're 3 of the top 5 most upvoted comments on the announcement thread... https://news.ycombinator.com/item?id=17221640 https://news.ycombinator.com/item?id=17221656 > I'm legitimately curious as my use of GitHub hasn't led me to notice any change Nor I. That's not that point. For the record, I think Microsoft has done wonderfully for the dev community in the last 10 years. I don't s…

concern of negative impact =/= negative impact. Great job twisting the truth. Im not gonna be surprised if you say you're a journalist.

Re: NPM Is Joining GitHub

#435
post #260

Earlier quoted context omitted.

It is exciting to see that having everything in a single application is being validated by GitHub. Last year it was very clear they are switching from a marketplace model to a single application by including Verify (CI), Package, and Secure. We think Git(Lab|Hub) will become the two most popular solutions and we look forward to this competition https://about.gitlab.com/handbook/leadership/biggest-risks/#... I think t…

> It is exciting to see that having everything in a single application is being validated by GitHub I wish Gitlab would get over this passive-aggressive negging of GitHub. I would squirm seeing something like that among any two competing companies. But it takes a strange configuration of overcompensating an inferiority complex to use it for the specific case of one company starting out as an explicit clone of another…

I don't think GP's comment was negging or passive-aggressive at all. The original GP said "That must make you nervous over at GitLab, no?" so it only seems rational to explain that they see this as validation and not as a risk.

Somehow, you took this explanation of why they aren't worried about this and turned it into a passive-aggressive stance..

Re: NPM Is Joining GitHub

#436

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…

Given that Microsoft for all intents and purposes killed Atom (along with their really promising xray project [0]) almost immediately after the acquisition [1] even after explicitly claiming they wouldn't [2], please excuse me for not seeing the GitHub acquisition in the same positive light.

[0] https://github.com/atom-archive/xray

[1] They never officially announced it, but they almost certainly de-staffed it to the point where it's barely on life support: https://imgur.com/a/jQBHsUk

[2] https://www.reddit.com/r/AMA/comments/8pc8mf/im_nat_friedman...

Update:

What a surprise, the VSCode fanboys are coming in droves to downvote and say nothing more than how Atom was going to die anyways.

Sure, maybe it was, but that's not the point. The point is Microsoft _actively pulled development resources away from Atom after explicitly claiming they wouldn't_.

I get that a lot of people like VSCode better than Atom, but _please_ put things into perspective for a moment and consider if you'd make the same comment if the same thing happened to _your pet project that happened to be #2 in popularity but then got axed after being acquired by the company who owned the #1 after claiming they wouldn't do exactly that_.

Whatever your opinion might be on Atom vs VSCode, can we not at least agree that this kind of behavior is something we should hold acquiring companies accountable for? It might not make any difference to their bottom line at the end of the day, but the least we should do is hold them to the fire in the court of public opinion.

Re: NPM Is Joining GitHub

#437
post #398

Earlier quoted context omitted.

Amazon is! https://aws.amazon.com/jp/blogs/opensource/aws-sponsorship-o...

Ah, neat! Works out well for them; I assume it's relatively cheap to just serve an S3 bucket on their CDN (though I guess bandwidth costs may rise rather dramatically if Rust ever reaches Node levels of popularity), while not taking on any other operational expenses of actually running a registry.

CDN bandwidth by nature of the reach of Cloudfront will mostly be offload onto the local peering fabrics. It basically costs nothing in per mbit billing - e.g. linx https://www.linx.net/wp-content/uploads/2017/10/Fees_Schedul.... 100gb hand. That's not to say there aren't other major costs in running a resilent edge network which go someway to justify 0.0Y/GB pricing where Y varies from 1-9 depending on location for non sponsored projects. tl;dr - it won't ever be a problem

Re: NPM Is Joining GitHub

#438

Earlier quoted context omitted.

Before someone else comes along and writes a monologue, the biggest downside might be how it handled (didn't break) its contract with ICE[0]. If the acquisition didn't happen, old GitHub might've dropped the contract immediately upon enough employees speaking about it. 0: https://news.ycombinator.com/item?id=21412600

That's a subjective political opinion of a far-left vocal minority. Not everyone has an issue with ICE (a federal law-enforcement agency that stops criminals and saves lives) nor finds a problem with a company legally providing services to the government.

The fact that ICE has built concentration camps (as verified by scholars who study concentration camps) is a fact, not a subjective or political opinion. The fact that there are children in these camps, many being raped, some being tortured, is also a documented fact, not a subjective opinion.

These are well-documented facts that have been widely reported on in the mass media. You can find links to specific articles on my blog in the recent article about Microsoft and GitHub, if you wish to learn specifics.

The kids are in there right now, as I write to you.

Whether or not Microsoft's provisioning of services to the government is "legal" or not is not particularly relevant to the thread, but it is interesting that you bring it up, presumably as a defense of their behavior.

Again: This is not a partisan thing. At all. Your attempt to reduce it to such is inaccurate (and, tbqf, off-topic for the thread about Microsoft-the-corporation, as well as off-topic for HN).

https://galaxypress.com/inspired-philip-k-dick/

Re: NPM Is Joining GitHub

#439
post #406

Earlier quoted context omitted.

I guess every person who was put in a cage near the border of the US was a huge danger. https://www.aclu.org/issues/immigrants-rights/ice-and-border...

To keep this as straightforward as possible: Illegal immigration is a crime and is enforced just like any other. Committing crime can mean incarceration, which many US citizens face everyday. It has nothing to do with being a "danger", but when you don't have permission to even be in the country then there's no bail or other release possible. Also detainment centers are not cages but fenced areas with free movement i…

https://www.nytimes.com/2019/02/27/us/immigrant-children-sex...

https://www.newyorker.com/news/q-and-a/inside-a-texas-buildi...

Re: NPM Is Joining GitHub

#440

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…

Given that Microsoft for all intents and purposes killed Atom (along with their really promising xray project [0]) almost immediately after the acquisition [1] even after explicitly claiming they wouldn't [2], please excuse me for not seeing the GitHub acquisition in the same positive light. [0] https://github.com/atom-archive/xray [1] They never officially announced it, but they almost certainly de-staffed it to the…

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 measure, look at VSCode's:

https://github.com/microsoft/vscode/graphs/commit-activity

The number of commits per, uh, date unit (the graph is not super clear on that axis, honestly) across the entire length of VSCode's activity graph rarely drops as low as the highest number of commits per date unit for Atom.

I'd have preferred to see both survive and do well, but that really hasn't been the way the text editor space seems to have worked. Editors that are conceptually awfully similar to one another tend to have one dominant player: TextMate (at least for Macs), then Sublime Text, then Atom, then very quickly Code. Given that Code and Atom are probably the closest of any two in that list, this just isn't that surprising.

Post reply on HN