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

531–540 of 588 posts

Re: NPM Is Joining GitHub

#531

Post by LandR »

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.

I see freedom of speech starts and ends at the government can't compel or supress your speech.

Your employer or society in general absolutely can via the consequences of what you say. If you are making your employer look bad then they can and should be able to get rid of you.

If society decides they don't like you because of what you say and choose not to associate with you or use your business than that also feels fair enough.

Re: NPM Is Joining GitHub

#533

Post by CodeCube »

_pmf_ wrote: post #478
manigandham wrote: post #329

Earlier quoted context omitted.

What's wrong with Microsoft's dev strategy? .NET continues to be the most powerful and productive platform that I've used. .NET Core was a great move and it's all coming together nicely now, and even creating innovations like Blazor.

The flip flopping between Metro / Windows 8 / UWP permanently turned me from doing anything non-win32-API on Windows again.

That debacle was an entirely different chain of management that is no longer at the company ;)

Re: NPM Is Joining GitHub

#535

Post by abstractbarista »

CSMastermind wrote: post #508
Galanwe wrote: post #479

Earlier quoted context omitted.

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

I'm not at Microsoft anymore but I was there when Skype got acquired and I had a bunch of friends who worked on it. You have to understand that the technology underlying Skype at the time was very brittle and poorly designed. Google almost bought Skype before Microsoft did and backed out after they got a look at the code. When Microsoft acquired it Skype was routing its traffic over port 80 for example.

Port 80 isn't necessarily a problem? Sounds like a great way to get around restrictive network devices like firewalls. Encryption is a thing right?

Re: NPM Is Joining GitHub

#536

Post by abstractbarista »

CSMastermind wrote: post #515
grandpoobah wrote: post #512

Earlier quoted context omitted.

Isn't using port 80 a trick to avoid being blocked by firewalls?

People would say that but most firewalls block _incoming_ port 80 connections so that logic never held much weight.

Many networks like in hotels and airplanes only allow out on port 80 or 443.

Re: NPM Is Joining GitHub

#537

Post by _ea1k »

CSMastermind wrote: post #515
grandpoobah wrote: post #512

Earlier quoted context omitted.

Isn't using port 80 a trick to avoid being blocked by firewalls?

People would say that but most firewalls block _incoming_ port 80 connections so that logic never held much weight.

That isn't really relevant to the problem they were working around. The problem is that many firewalls block outbound ports other than port 80, 443, and some other very common ports.

Put another way, if both sides block 80 incoming, their only hope is fancy NAT-punching techniques.

But those NAT-punching tricks are useless if they are using a port that is completely blocked on the outbound side.

Re: NPM Is Joining GitHub

#538

Post by sequoia »

lewisl9029 wrote: post #436
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…

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…

> Microsoft for all intents and purposes killed Atom

I don't think so. When VS Code came out my reaction was "Wow! It's like a 1.0 version of Atom!" I.e. an electron (or similar) based editor that works, whereas atom always seemed like a beta release. I tried to use atom a bit but it came with little out of the box and the plugin ecosystem was a complete mess. I filed an issue asking if obsolete/dead plugins could be somehow removed from the plugin repository, but nothing came of it.

Atom wasn't killed, it died on its own.

Re: NPM Is Joining GitHub

#539

Post by sequoia »

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…

From Microsoft's perspective, what's the advantage to them or their users to pay for two somewhat similar free offerings to be worked on in parallel? Given that one was gaining in popularity by leaps and bounds while the other was rapidly losing market share and relevance, what course would you recommend? "Fund both indefinitely, to keep the handful of atom users that want new features happy"? Be reasonable.

Re: NPM Is Joining GitHub

#540

Post by tekknik »

ratww wrote: post #519
slow_donkey wrote: post #491

Earlier quoted context omitted.

Ooh details please. I've looked at the docs but haven't used actions yet. What makes it worse than circle? The initial capabilities look similar and circle really needs a competitor with how flaky their service has recently been.

Nah, Github Actions is actually amazing, and has been rock solid for me. For someone who's not a pro in using CIs, it's been much easier to use than CircleCI. I never have to spend more than 20 or 30 minutes fiddling with Actions to make it actually work. This for me is the biggest contribution to open source: normal people like me (who don't want to get too familiar with proprietary or overengineered CI tech) will b…

I can’t speak for actions but you seem extremely biased for some reason. It would take you less time than it took to write this post than to learn circleci. Much less than 20-30 mins.

https://circleci.com/docs/2.0/hello-world/

Post reply on HN