> Probably TFS, which Microsoft use quite a bit internally But seemingly less and less so, especially in the SDK-teams. Which is definitely interesting. If Microsoft's own SDK-developers don't want to use Microsoft's own source-control and ALM-system, but rather prefers Github, what signals does that send? I would sayed mixed at best.
it's an open secret that TFS sucks ass. I dont think anything is going to change that attitude - they might as well use something better, and hence the move.
Not much of a secret. There was open revolt when we were forced to switch in MSN.
Perhaps Microsoft wants to divest out of the git+online tools space? Github is the incumbent that they did not crack how to beat and it will be a bit more crowded with Amazon who seems to be also coming this year with CodeCommit. So far, Amazon strategy has been to suck all air from the room.
Absolutely not. We are very committed to the git space, both on the client side (Visual Studio) and the server side (Visual Studio Online and Team Foundation Server). We're continuing to invest - in fact, we're hiring for git developer positions. (Send me a message if you're interested!)
This is about open source hosting which, to be quite honest, GitHub does better, and is where users expect our open source to be.
Even though Microsoft have embraced open source, they are not happy about the GPL license, and have actively replaced GPL code in their previous takeovers.
[IANAL] My impression is that GPL (or another copyleft style licence) would create incompatibilities with the business models of many of their customers. Taking contributions would also be problematic since Microsoft may wish to dogfood their opensource for proprietary products. For better or worse many of their products incorporate licensed technology from other companies under terms incompatible with GPL. So GPL's…
This. GPL is just really really hard to work around if you're selling non-SAAS products. In general, it's not something you try to do if you have any alternative. And nowadays, you almost always have an alternative. Increasingly often it's a more capable, more actively maintained, and better supported option that comes with the added bonus of not needing to take the time to get special approval from your legal department.
Probably TFS, which Microsoft use quite a bit internally [1]. [1] http://blogs.msdn.com/b/visualstudioalm/archive/2013/08/20/t...
> Probably TFS, which Microsoft use quite a bit internally But seemingly less and less so, especially in the SDK-teams. Which is definitely interesting. If Microsoft's own SDK-developers don't want to use Microsoft's own source-control and ALM-system, but rather prefers Github, what signals does that send? I would sayed mixed at best.
Well, we use GitHub to host our git repositories for open source and public projects. We use TFS to host our git repositories that are private and closed source.
GitHub does a great job hosting open source projects. TFS doesn't. I don't think this is a mixed message, we're using the right git hosting service for the job.
Free private repositories and out-of-the-box mercurial support. Works well for those small side projects which you do not (yet) want to maintain. I have lots of stuff in there which i want to keep as reference for projects to come and would never want to release to the public.
If you don't yet want to publish, why do you need GitHub or Bitbucket? Why not just keep the repository local?
As long as you are backing up your repo in some way, you don't. But these sites just make it easy.
Can someone please change the title to .NET Compiler Platform ("Roslyn") is moving to GitHub The current one makes it seem that MSDN is moving to GitHub (wouldn't that be a sight? :-)
I find this to be true of younger people who aren't aware of Microsoft's past and don't look at them with the sideways glance the rest of us do. In fact, I find it amazing how many younger people never even heard of their dark side and all the anti-trust movements on two continents.
Apple is more antitrust than Microsoft ever was. Bundling a browser with your OS (while still allowing users to install an alternative) is nothing compared to the restrictions in the iOS app store.
That's not an "anti-trust" action by itself and bundling the browser was only part of the issue against Microsoft in the US and more of an issue in the EU.
This is getting terrifyingly close to my prediction that Microsoft should/would/will buy GitHub. When I first started predicting this two or so years ago, it was mainly for its comedic value (it always got laughs, followed by "yeah, they should!" followed by nervous laughter followed by "wait, do you think they would actually do that?!"), but after the open sourcing of .NET I honestly think anything is possible. Espe…
What does MS gain? Is online source code storage really going to be a million or billion dollar business for them? It seems like it's just a race to the bottom with costs, just like Dropbox, Box, etc. etc.
"My father taught me many things here — he taught me in this room. He taught me — keep your friends close but your enemies closer." - Michael Corleone
Under-30 dev here. Been programming in C# for the past 3.5 years now, and loving every minute of it. I find VS and the associated tools be a far more productive and enjoyable experience than the Linux/Unix toolchains I was forced to use in undergrad, and C# to be a completely amazing language. The two warts, for me, are MSBuild (powerful, but obtuse at times, but still better than make) and PowerShell (again, powerfu…
>"Under-30 dev here. Been programming in C# for the past 3.5 years now, and loving every minute of it." Mid 30's here. I work mostly on C++ but I have to jump into C# code once in a while. I agree that C# is a very productive language and I love how it never gets in your way ("Do you say you don't want to use a common interface for your generics? Use dynamic!"). My only "complaint" is that C# is so indulgent that it…
C# is oft underrated, in my view. It's very quick to code in, is part of a large (if Windows-centric) ecosystem, and has been generally fairly tastefully designed. Compared to other languages you might compare it to, its designers aren't afraid to be a bit avant garde at times (unlike Java), it's got static typing (unlike Python), it's got garbage collection (unlike C), and... well, I know Go programmers hate it when people drop the G-bomb. But it's got that too. Unlike Go.