[1] https://medium.com/@moritzplassnig/github-is-doing-much-bett... (disclaimer: I wrote the article but the data is by Bloomberg)
[1] https://medium.com/@moritzplassnig/github-is-doing-much-bett... (disclaimer: I wrote the article but the data is by Bloomberg)
Your assertion can only make sense if you also believe that a 12% paycut is irrelevant to your income.
All of Github's competitors (i.e. gitlab and bitbucket) already offer unlimited private repos. This is Github catching up.
However, I don't think it will be an issue. As hosting costs drop to zero, if someone starts charging, they lose customers to a free competitor. (as is happening here).
There’s surely a goodwill factor and wider strategic benefits here beyond the relatively small amount of revenue - these individuals enjoying the free private repos will in many cases likely be future candidates for customers for the enterprise offerings etc, or one day find themselves involved in discussions regarding managed VCS for a larger org. Given Microsoft’s current strategy to win over developers, this seems like a pretty sensible move, and the price (for Microsoft) very low. Strategically this seems not entirely different to the free accounts AWS throw at university students. Once you have someone hooked on your free offerings, you can start locking them into the wider platform (Azure) much more easily. Again, pretty much the AWS playbook.
Also, let’s not forget the 12.5 percent figure comes from 2016, a year which saw some pretty significant changes to GitHub’s offerings, such as unlimited personal repositories for paying users among other things. Prior to this you had to pay more to get more private repos. The number today may be somewhat different - I know my github spend went down following that change.
Also, 12.5 percent of revenues - comparisons to a 12 percent pay cut are pretty misleading.
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.
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.
It's misleading because it ignores user acquisition & conversion. Freemium often means you "take a paycut" on option A in order to make even more money on option B.
It's misleading in the sense that a 12.5% pay cut is not something I can recover in other ways.
Meanwhile, there is a possibility that this 12.5% cut on individual account might be recovered automatically in other ways if it results in increased enterprise account.
My personal private repos have always been on BitBucket. Not because I like BitBucket more, but simply because of the additional cost.
Having unlimited private account on GitHub will encourage me to move my stuff there, and ultimately reduces the friction and increases the chance that at some time in the future I might be a paying enterprise customers.
Yeah, I take that deal every day of the week.
Beyond a certain hand-to-mouth income it is (e.g. 150K vs 132K).
And many people chose pay cuts over personally overworking or stretching their business too thin.
The overly trivial point being behind the parent argument is that 100% of your revenue if better than less than 100%. Which is not always the case in business.
Businesses and freelancer drop gigs all the time to concentrate on where their main income is coming from. If you have a difficult customer or few demanding customers that generate just 20% of your income, it's often wise to drop them to focus on your easier 80%.
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 personal stuff. Now that I did move everything, I actually enjoy Gitlab quite a bit.
What do you think I'm going to use if I start a commercial project? In the past I would have chosen Github, but now that I'm comfortable with Gitlab and see all its benefits, it's probably the one I would choose.
Cutting that 12% may lose 12% in the short term, but in a few years, it's going to gain you much more than 12%.
If you think about mid-sized software companies (~10-100 devs), if 80% of your developers have a strong preference for Github over Gitlab or Bitbucket, then that company is likely going to stick with Github or decide to move to Github eventually. I think this is where Github captures much more than that 12% revenue that they are giving up right now.
I moved all my personal repos to Bitbucket a while ago, as it was free, and have referred them several paying customers from my clients.
Now, if personal accounts were far less (e.g. 1% of revenue), I could see the argument that they're irrelevant.
Maybe I'm just complaining about vocabulary, and perhaps your clarification was what the OP intended.
If that WERE the reason, they'd be charging for visual studio code, not giving it away.
Unless .. all github revenue is irrelevant for Microsoft - which might be true, for all I know.
Source: I am the CEO of Sourcegraph and consider similar things.
But in reality, the source of your customers' income has little to do with value. B2B is favored because the margins are generally higher.
Meh, just fire 12.5% of the staff. /s
As a particular former Microsoft CEO put it: "[…] DEVELOPERS DEVELOPERS DEVELOPERS DEVELOPERS […]". That strategy/desire hasn't exactly stopped, though it's certainly transformed quite a bit over the last couple decades (and Microsoft is finally actually getting somewhat effective there).
With this change, Github foregoes a little revenue in exchange for securing the vast majority of their revenue.
It turned out to be damned easy (and very cheap) and that's a serious threat to github's future growth because once people start to default elsewhere for one type of their work, it tends to drag along other types of their work.
But, for one very obvious reason, people have grown more and more interested in finding alternatives to Github, and they're forced to compete.
Gitlab and Bitbucket both heavily positioned themselves against Github with their unlimited private repos feature. With this competing with Github is going to become much harder. I think it's a smart move for MS.