141–150 of 225 posts
Earlier quoted context omitted.
It's reasonably easy to pick up your repo and leave. How easy is it to pick up your bugs and leave?
Reasonably easy: https://github.com/gitlabhq/gitlab-recipes/blob/master/impor...
Earlier quoted context omitted.
Also like Bitbucket, and agree with the interface. They made things responsive a while ago, and there were lots of complaints about the 'create a README' decision as a space-waster, they haven't done anything about it since. I like their revenue model, but because of the existence of JIRA and Stash, Atlassian are refusing/reluctant to improve the issue tracker in Bitbucket. For example, I can't manage releases, creat…
Bitbucket has issue with cross-referencing. You can reference an issue from an issue but to make a two-way reference you need to edit both. This is a showstopper for projects that use tracker for planning too, not just for logging bugs.
Earlier quoted context omitted.
What's better about Bitbucket? I've never used it, just wondering.
If you're working in a team the code review workflow is a bit better, because as a reviewer you can explicitly Approve a pull request. I've used it in a team where the requirement was to get two approvals before a pull request can be shipped. Having the number of approvals visible on the pull request list/overview screen is a tiny detail, but very useful. At my current job we're using a "ship it" label on GitHub to t…
Earlier quoted context omitted.
I like Bitbucket and have been using them for some time but their interface is slow and not as intuitive as Github's.
I stick with bitbucket mainly because of the pricing schemes. I create a lot of tiny private repos for company related work, sometimes just scripting type programs with only 5 files in it, and I can't afford to pay for each of those on github. Otherwise, github is just the best in the business in every aspect
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…
"Only if Github is selling." Everyone is selling, for the right number of billions. "We are excited about this new stage, because we are better positioned to ..."
Every monopoly is bad. GitHub is becoming one. I don't think it's a good move, as well as Google abandoning Google Code.
Earlier quoted context omitted.
I love TypeScript, and I wish it was more popular outside Microsoft, but it isn't.
I'd say it's relatively popular. It's also growing quite quickly: http://blog.javascripting.com/2014/07/28/fastest-growing-new...
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?
As long as you are backing up your repo in some way, you don't. But these sites just make it easy.
Earlier quoted context omitted.
>"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…