Live data from Hacker News

Announcing unlimited free private repos

blog.github.com

521–530 of 716 posts

Re: Announcing unlimited free private repos

#521

Earlier quoted context omitted.

> Nobody believes in supporting Microsoft as a company. I believe Microsoft has been doing amazing things for developers the past few years.

Sure, but you're not going to give Microsoft money because you like them and want them to do well, and that was probably the main motivation behind paying for private repos. It was never purely a value proposition of, "private repos are worth $8/mo", it was a value proposition of, "Github is a valued part of the community and I'm willing to pay a token subscription fee in exchange for some token extra features". Part…

Bitbucket offered free private repos and was struggling before it was acquired by Atlassian.

Re: Announcing unlimited free private repos

#522
post #351

So, when I go to downgrade my Pro account to the Free tier, it warns me: > You will no longer have access to unlimited collaborators or advanced code review tools in private repositories. > You will still have access to unlimited private repositories. So it seems some functionality beyond just unlimited collaborators that is tied to the Pro account - but the blog post makes no mention of what these "advanced code rev…

What I see is only: > If you downgrade, you’ll lose access to advanced code review tools in your private repositories.

Not super clear from above posters.

This sort of explains things better now:

https://github.com/pricing#compare

Essentially you lose:

Protected branches, CODEOWNERS, insights, wikis and pages.

Re: Announcing unlimited free private repos

#523
post #420

Earlier quoted context omitted.

> It's fair to say that the personal accounts are irrelevant from a revenue perspective. Your assertion can only make sense if you also believe that a 12% paycut is irrelevant to your income.

> Your assertion can only make sense if you also believe that a 12% paycut is irrelevant to your income. You only see the short term. I was on Github during my university, all my projects were there, my team mate were on there too, it was pretty great. When my student account expired, I decided to move everything to Gitlab. I didn't want to move but I won't pay 7$ a month to host my old school projects and some perso…

I can say the same, except in my case it was moving from Github to Bitbucket. If Github, did this a while back I would have been locked in for life (by choice)

Re: Announcing unlimited free private repos

#525
post #522
post #351

Earlier quoted context omitted.

What I see is only: > If you downgrade, you’ll lose access to advanced code review tools in your private repositories.

Not super clear from above posters. This sort of explains things better now: https://github.com/pricing#compare Essentially you lose: Protected branches, CODEOWNERS, insights, wikis and pages.

And those only for private repos; they're still available for public repos.

I've been happily paying Github $7/mo for years now for Pro, but there's now literally no reason to keep doing so, so back to Free it is. Thank you Microsoft! ¯\_(ツ)_/¯

Re: Announcing unlimited free private repos

#526
post #398
post #196

Earlier quoted context omitted.

I'm sure they apologized to Github, even if they didn't apologize to you for reading it.

Ah that's good to know. Do you have a copy of the apology? Sadly, I don't have access to Chris Wanstraths email.

I'm sure Microsoft will be fine

Re: Announcing unlimited free private repos

#527
I wanted to take a moment to point something out.

I think most people here would agree that "unlimited free private repos" is not considered lying when in fact the free private repos are limited to 3 collaborators... correct?

So why is it that when the subject turns to cell phone data, suddenly "unlimited data" is considered lying when the speed is then limited past a certain point?

(Yes, I get that one service is paid and the other is free, and that you don't look a gift horse in the mouth, but those are beside my point.)

Re: Announcing unlimited free private repos

#528

Earlier quoted context omitted.

When GitHub's financials got leaked in 2016, GitHub's personal accounts accounted for 12.5% of their revenue. GitHub Enterprise was 50%, their organization (= business) accounts were the remaining 37.5% [1]. It's fair to say that the personal accounts are irrelevant from a revenue perspective. [1] https://medium.com/@moritzplassnig/github-is-doing-much-bett... (disclaimer: I wrote the article but the data is by Bloom…

> It's fair to say that the personal accounts are irrelevant from a revenue perspective. Your assertion can only make sense if you also believe that a 12% paycut is irrelevant to your income.

You're missing why Microsoft purchased github in the first place. It wasn't for the personal account revenue - which isn't even a rounding error on their earnings report even if it is 10x what it was when revenue was leaked in 2016 (at which point it was $17.5 million/year).

If that WERE the reason, they'd be charging for visual studio code, not giving it away.

Re: Announcing unlimited free private repos

#529

Earlier quoted context omitted.

So why don't they hide or pull the post down until tomorrow?

I’m guessing the post had already gone viral. Wouldn’t it be great though if you could kill content from the internet by simply removing the source. Privacy concerns would probably become less of an issue.

You pull the content down not to try to put the cat back in the bag. You pull the content down to show your source that it was an honest mistake and you aren't trying to capitalize on the "scoop".

Re: Announcing unlimited free private repos

#530
post #350
post #340

Earlier quoted context omitted.

Comparing 12.5% revenues to a pay cut is not misleading at all. Unless there is some reason to believe that making individual accounts free will somehow also reduce costs in a material way. Seems to me it will likely increase costs significantly as many more users will flock to create free private repos. In fact, it's more like giving you a 12% percent pay cut and then asking you to commute further to work.

Focusing solely on the impact to Github’s bottom line kinda misses the entire point of Microsoft wanting to acquire them in the first place. A decision like this has to be viewed in the wider context of Microsoft’s market strategy and the rest of their developer tool portfolio, of which Github is just one piece. If Microsoft just cared about short term gains, there were much better ways to blow 8 billion dollars.

Indeed -- seems to me that the recent MS moves with Github are part of the same thought process that led them to include Bash / WSL in Windows 10.
Post reply on HN