Microsoft’s Github Acquisition – An Unbiased Perspective
As someone who has worked on Microsoft tooling since the days of Foxpro 2.6 to Visual Studio 2010 in IT career, and yet ditched them all for PHP, Python and open source years later, I think I am qualified to offer a somewhat neutral or objective perspective on this acquisition.
When this news was first announced on last Friday, I was naturally puzzled and so were a lot of other developers and not without reasons. The way this was initially announced without any clarification or their plans about what they were going to do with the hosting facility in future, speculations were bound to be raised and people were bound to be pissed off, especially given Microsoft’s history of being “not so friendly” with open source and “not so good” with some acquisitions.
When it comes to open source, the Linux subreddit is the place where developers pour their hearts out and this particular thread quite summed up their initial knee-jerk reaction. As the most upvoted comment says:
its like Microsoft is obsessed with generating as much frustration in the world as possible
Other reactions were also quite similar:
First, Sourceforge started to install malware on the open source projects. So everyone run to Github. Now, Github might get owned by Microsoft. Not to mention Github is 100% closed source. Gitlab looks good every day. There are other open source git solution too.
GitLab, the top open source competitor to Github soon became the most discussed alternative (apparently, their marketing team did their bit too with the perfect timing!). And so, a mass exodus of projects soon began, which not only became the most discussed topic on reddit, but also caught a lot of media attention too:
Just within a couple of days from this announcement, some 13,000 projects had already migrated to Gitlab which included some prominent names. Naturally, it was time now for Microsoft to do some damage control. But if their PR team was any wiser, they should have already anticipated this and this damage control move should have been done at the outset as the first thing. How could they not expect this backlash considering Microsoft’s past history with open source (however distant it may be)?
The first move came when Satya Nadella, the Microsoft CEO gave an interview to CNBC on Monday (4th June):
One of the most important things Satya said in the interview was that Microsoft is a developer tooling company at core (let’s ignore Windows and Office for a moment!). However, most developers still had concerns, they wanted to know how this high level strategy of being open source developer friendly will turn out to be in practice.
Most importantly, they needed an assurance that their daily driver for source control isn’t going to be integrated and hijacked by other Microsoft products like Skype, Linkedin or even a Passport account. And that assurance came yesterday from Nat Friedman, the future CEO of Github in his Reddit AMA.
Firstly, the fact that Github Inc. was going in the hands of an open source veteran who had contributed to GNOME and MONO projects in the past was itself quite reassuring. At least, Github isn’t going to be controlled by a typical corporate honcho who has nothing but shareholders’ interests in mind! Nat assured most redditors that Github is going to stay as it is, its developer focus is not going to be shifted, nor is it going to be integrated with any other products. And most importantly, they will never require a Microsoft account to login to Github, rather, their other products might consider allowing a Github user to authenticate to their systems in future:
Nat also goes on to further assure redditors in the AMA that they will always remain a “developer first” company, and are keen to learn a lot from Github from this acquisition. Rather than impose their own work culture on Github, they’ll be taking lessons from Github and try and be like them:
All in all, this damage control or whatever Microsoft has done seems to have done the magic at least for the moment. People and projects seem to have stopped their exodus to Gitlab, though its difficult to say what could happen in the long term.