201–210 of 225 posts
"We’ll be using GitHub Issues for both discussions and bugs after the switch" Hilarious! Did someone call GitHub "social"?
Not sure I understand? I would say that GitHub is quite social. It's pretty much the Facebook of code hosting.
Earlier quoted context omitted.
If you don't yet want to publish, why do you need GitHub or Bitbucket? Why not just keep the repository local?
> If you don't yet want to publish, why do you need GitHub or Bitbucket? Why not just keep the repository local? My two cents on this are that I always try to outsource any internal services to reduce maintenance time. For example 1. Own git repository will need backup and server configuration to be accessed from all machines that I own, which means I will need to spend time on security. 2. Own GitLab instance will m…
Earlier quoted context omitted.
> 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.
Earlier quoted context omitted.
Not sure I understand? I would say that GitHub is quite social. It's pretty much the Facebook of code hosting.
No way to hold discussions though. How social is that? How do I ask a question (which is not a bug or a feature request)? Go to some completely different site?
Earlier quoted context omitted.
Get a monthly subscription. They limit you by number of team size, not number of repos.
I was thinking more like ditching github altogether and publish everything on Bitbutcket
Earlier quoted context omitted.
This isn't big because Microsoft has stared sharing source. The source to the .NET framework has been available _without_ ILSpy for years now. This is big because Microsoft is truly embracing an open source development model. They've opened most of the .NET platform up to the whole shebang - pull requests, copying code into other projects, forking, all that good stuff.
So the big deal is that we're now allowed to modify the code of a few libraries? Fair enough.
MS moves to open source parts? People Bitch.
Can't win...
Earlier quoted context omitted.
And yet, they bought Minecraft, which seems to be exactly that strategy.
I don't think MS bought Minecraft for image. I think they bought it because it's very successful and has a chance to make a ton of money.
Earlier quoted context omitted.
Microsoft's development tools are (therefore) expensive, so unless you're getting paid to use them, it's harder to invest yourself in them.
Plus you can be locked out of VS if you go away for a weekend and haven't signed into the IDE in a while. Happened to me twice last year. Let me repeat that - they force you to login to their tools (that Ive paid for) and if you don't the IDE is rendered unusable. Fuck the guy in the VS team that OK'ed that feature. But it was a blessing in disguise really as it made me look into other pastures like Node & Laravel.
Earlier quoted context omitted.
I've been listening my way through the archive of Scott Hanselman's hanselminutes podcasts. Microsoft has been striving to be on the right side of history in regard to open source for five or six years. It's all out in the open. Moving to Github is simply developer friendly. Don't misunderstand me. Microsoft's products compete with open source software in the marketplace for developer mindshare and I am not suggestin…
> It's all out in the open. Really? So they release the source to a few of their developer frameworks and tools, and they're now "all open"? Don't get me wrong, as a long time C# developer I do appreciate the gesture and I'm especially happy that they're working their "not invented here" mentality, but with simply providing us with the source code that we already have anyway (via ilspy), all of this just seems over-i…