I completely agree with your comment. As much as I love Microsoft, this is a weird development.
It’s like if Google bought Mozilla and Firefox became just another Google browser.
It’s like if Google bought Mozilla and Firefox became just another Google browser.
Microsoft rescued them.
'Extinguish' might be right, but Amazon is the target here and holding off Google in second place. Other cloud providers will have to race to the bottom if they are not already there.
Microsoft wants people to develop for Windows, because with no apps you have Windows Phone. If what you want to use runs on Windows, Windows is what you purchase (or in a few years probably subscribe to along with Office 365 and OneDrive). A lot of that subscription model already exists on the Enterprise side of Windows, and I don't think anyone would be surprised to see it expand - "Windows as a Service" has been a topic of discussion for years now.
- It allows them to peek into any private repo on GH right from their own office. All major players host code there, likely a lot of them in private repos too. Microsoft has a large trackrecord of 'me too' products (i.e. the ones released after the original from another company is successful) and corporate espionage isn't something that's just happening in the movies. This too could make things very profitable
- Developer relations across private repos could increase the value of linkedin profiles which in turn could make that more valuable.
But that's about what I could come up with. I seriously don't understand why one would spent $2B on github if it hosts your OSS stuff. Also, to make sure VSTS become more successful with an integration doesn't make sense to me: GH isn't the most profitable service out there and was losing money. Hell it might even go belly up sooner or later and VSTS would look to be a better alternative.
That sounds incredibly unlikely if not borderline ridiculous.
Allows logically, not legally though I'd expect.
I imagine, in my paranoia, the first thing MS will do is change the T&Cs.
How did they become unprofitable? Their expenses are servers and people. It seems that there are an enormous number of companies paying for private repos and that should more than cover their costs.
https://www.bloomberg.com/news/articles/2016-12-15/github-is...
I'm guessing it was from corporate mismanagement, overbalooned salaries for initial employees, and probably hiring too quickly to meet demand.
They want to be a player in that game, so they’ll transition off they are old product which isn’t that popular onto a new one they purchased that has all the mind share.
As long as they don’t screw it up, and recent Microsoft seems to me like a company that won’t, it will benefit them. And perhaps it will benefit the user some to do have a company with deep pockets behind it.
Makes sense they try to control the future of the tool they use in so meny projects.
> Torvalds turned over maintenance on 26 July 2005 to Junio Hamano, a major contributor to the project.[25] Hamano was responsible for the 1.0 release on 21 December 2005, and remains the project's maintainer.[26]
I'm guessing Torvalds still has a lot of control if push came to shove, so we can assume git is executively controlled by Torvalds and Hamano.
I think git and decentralized source control are great, but I get a little suspicious of people saying tooling is "not fun" simply because it isn't their favorite or most familiar.
I like it, and really love that they added web interface (review, overall view of changes, etc.).
P4 is very easy to get started, all you need is to learn several things, and tools underneath can easily be changed, learned to do this for you. Then it's easy to comprehend changes, since all CL's are monotonically increasing, so once gets perception when a CL is announced whether it affects him, or her, etc.
And the elephant in the room is the really, really huge files: psd, tiff, max, maya (ma/mb) models, fbx, zip, iso, exe installs, etc.
There are some peculiarities, like text files handling and conversion (e.g. \r\n <-> \n).
Then some useful (but controversial) features: locking (per extension), or manually per file.
Having all your projects from different teams in one place, but each team/project can customize a view to its own work (a bit opposite of what google is doing with their mono-repo, but unlike g4 there ain't option to sync only what you want, and have the rest off the network).