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

Hello, GitHub

natfriedman.github.io

Post reply on HN
Print view View original

321–330 of 671 posts

Re: Hello, GitHub

#321

Post by jenscow »

sdesol wrote: post #283
fishywang wrote: post #225

Earlier quoted context omitted.

I agree that people are overreacting, but I think the overreacting is good for git in general. It helps smaller players (Gitlab, etc.) to break the monopoly of Github, and reverse the wrong conception a lot of new developers have that git == github. Remember git is supposed to be decentralized? In reality it's actually centralized on github, and github is becoming the single point of failure on the developer world, w…

> It helps smaller players (Gitlab, etc.) to break the monopoly of Github Or do the opposite. If Microsoft decides to make private repos on GitHub free, I can see VERY big issues for other players. I suspect more people use GitHub alternatives for cost reasons, rather than ideological ones.

The 3rd E.

Re: Hello, GitHub

#322

Post by luckydata »

dlisboa wrote: post #156
justadudeama wrote: post #121

Earlier quoted context omitted.

What is so negative about LinkedIn?

Almost everything? Aside from keeping an updated resume I've never had a single job come from it, nor anyone I know. As far as networking it's useless too. It's just recruiter spam and people you never met adding you to their network. They also did the whole MITM attack on your e-mail's contacts a few years back. None of that is Microsoft's fault though, it's been useless for a while.

That's, like, your opinion man. Most of my jobs and most of my friends jobs have come through (or discovered thanks to) Linkedin. Before becoming an employee I used the site to find cofounders, people to interview for product feedback, check the background of possible hires...

You don't use it or like it, fine. Linkedin has created economic opportunity for so many, it's kinda ridiculous to dismiss it out of hand.

Re: Hello, GitHub

#323

Post by jodrellblank »

SiVal wrote: post #304
hirsin wrote: post #279

Earlier quoted context omitted.

Not entirely true. Microsoft puts (almost? Yet to find anything that isn't) all our code on VSTS which is accessible remotely, without VPN. I've checked in a (very very minor docs) fix to the Windows code base from my Android phone over LTE.

That's amazing. Contrast that to my friend who works on code at Apple that's so guarded that he can't even access it from Apple HQ. He has to travel to his office in an unmarked Apple bldg several miles from HQ (in an unmarked van) and access the code from inside the bldg. Any attempt to work on his code outside that bldg, on the Apple employee shuttle for example, will result in immediate firing with possible crimin…

LOL-worthy

and yet, which company released an OS update with an open root account with no password, patched it in a way that broke file sharing, then a couple of months later released an update with another password bypass bug? Hobbling people with security theatre isn't begetting good or secure code.

Re: Hello, GitHub

#325

Post by sequoia »

thiagocsf wrote: post #256
oaiey wrote: post #165

Earlier quoted context omitted.

The Microsoft bashing is painful. I also wonder about outcomes like that, positive ones for Microsoft, GitHub the platform and GitHub the community. So much negativity!

Painful... for you. On a serious note though, they deserve all the skepticism coming to them. I know they’ve been working in the last few years to revert their status as OSS public enemy #1 but remember, this is the company that said the GPL is cancer. Let them earn our trust. Keep the pressure, stay vigilant and be ready to change vendors.

> remember, this is the company that said the GPL is cancer.

You must greatly mistrust the StartupNews community as well, as "gpl is cancer" gets said here almost daily as well. d:o)

Re: Hello, GitHub

#326

Post by swayvil »

luckydata wrote: post #313
swayvil wrote: post #310

What does M$ bring to the table other than a giant pile of money? How does this giant pile of money serve the users of github?

Other than being the biggest developer-focused company in the world? Having an extremely complete set of developer tools that can integrate with github? A cloud computing service to deploy apps? I guess nothing, it brings nothing to the table.

I think that Microsoft is money-focused, not developer-focused.

Correct me if I'm wrong, but the mass of open-source developers vastly outweighs Microsoft.

These "developer tools" are the property of Microsoft. Which suggests an obvious and worrying path in Github's future. Tell me that I'm wrong.

Everybody and his dog has a cloud computing service these days.

Re: Hello, GitHub

#327

Post by mathgeek »

VectorLock wrote: post #272
Klathmon wrote: post #129

Earlier quoted context omitted.

Personally, I'm not "bailing" from anywhere. I am however using this as an opportunity to rely on any one single place less . I'm in the process of mirroring my git repos on GitLab, and trying to think of a way to signify that both the GitHub and GitLab repos are "canonical", and that issues/PRs/contributions can happen at both.

Sounds like that would be a pain having that kind of work done in two places.

Which is rather unfortunate for something that all revolves around git.

Re: Hello, GitHub

#328

Post by saagarjha »

SiVal wrote: post #304
hirsin wrote: post #279

Earlier quoted context omitted.

Not entirely true. Microsoft puts (almost? Yet to find anything that isn't) all our code on VSTS which is accessible remotely, without VPN. I've checked in a (very very minor docs) fix to the Windows code base from my Android phone over LTE.

That's amazing. Contrast that to my friend who works on code at Apple that's so guarded that he can't even access it from Apple HQ. He has to travel to his office in an unmarked Apple bldg several miles from HQ (in an unmarked van) and access the code from inside the bldg. Any attempt to work on his code outside that bldg, on the Apple employee shuttle for example, will result in immediate firing with possible crimin…

> unmarked van

You may think it’s unmarked, but if you know how to spot them they’re very easy to pick out.

Re: Hello, GitHub

#329

Post by Rapzid »

Klathmon wrote: post #170
bitL wrote: post #151

Earlier quoted context omitted.

I wouldn't be worried about Atom; half of Facebook is using it; if anything were to happen, they would fork it.

While i'm confident that Atom will not "die" any time soon, if MS pulls the team that's currently working on new features and reassigns them, then at best it's going to be a large blow to the project. A fork won't have the same team working on it, a fork won't have the same domain knowledge over the internals, a fork won't have the roadmap or what was currently planned and how to do it, a fork won't have the same uni…

MS wouldn't pull the team; it would be GitHub that pulls the team. GitHub is operating as an independent company.
Post reply on HN