I'm not asking for that, but making wild baseless predictions of how the service will go to shitter or how suddenly all private code will be ripped off and "I'm going to gitlab now, because Microsoft sucks!" is not part of a healthy discussion.
I do have some privacy concerns but they're no less than when Github was not owned by an enterprise software company; If anything I'd be more concerned about privacy if it were Google or Facebook making this acquisition.
The problem is deeper than that though. Unless you were developing an Editor or a Git hosting service, you were not in direct competition with GitHub. Suddenly a lot of startups will find their private code hosted by a direct competitor. I wouldn’t feel comfortable if I was them.
While it's not a complete 1-1 mapping, I keep thinking of Stac Electronics disk compression lawsuit against MS when it comes to handling source code:
To be honest, even with regards to private repos, I can't see Microsoft reading the source code because that would be a massive law case waiting to happen. What I'm more concerned about is Microsoft trying to integrate more of their own suite into Github. I'm also concerned about the future of Atom; which I specifically chose over VSC because it wasn't managed by Microsoft.
Not that because it happens, it is nice; but at-least at this point the source code access concern is more of a conspiracy theory if anything.
All I need do to have concern about this acquisition is look to last year. https://archive.codeplex.com/
How long before they get bored of github then? Codeplex wasn't as good or popular as github, but did seem to have many valid reasons for existence if you were Windows focused. So they killed it.
But they're not baseless predictions, they're based on past information and it tells us it would be prudent to minimize reliance of Github sooner rather than later.
It knows what these things are. If it wants to stop doing them, then I'm happy to use some of its products. Until then, I'm going to gitlab now, because Microsoft sucks!
If the company that ships OS with preinstalled, hidden keyloggers (using that as a pars pro toto) acquires the platform I host my code on, that's not a basis on which to be concerned?
If it's the first, that's not exactly Microsoft's fault, in the same way it's not exactly Mocrosoft's fault that if you buy a Dell it might come with McAfee preinstalled.
Although, it could be argued that if the driver was verified, perhaps they should extend their verified driver program to cover that instead of just crash protection. Then again, since the arguments here are centered around not trusting Microsoft with your source code, I can see why they may not require that...
MGS did right by Bungie/Halo circa XBox; though Halo hadn't yet been released, and it's initial fanbase were all Marathon fans.