Hacker News Reader

Comment by ohitsdom | Hacker News Reader

Love the new Microsoft. For small side projects/prototypes, I have tended to not use version control (I know, the horror). I just stumbled across their free private repo storage this morning, and it's going to be a huge improvement in my at-home workflow.

View on HN

https://bitbucket.org/ and https://about.gitlab.com/ have free unlimited private repositories. Both are excellent.

It's also a pretty good use for a VPS, too. I mostly just use local version control for my stuff, but I enjoy being able to just push to the Mercurial repo on my Linode whenever I want to back stuff up.

Indeed, plus it's fun to learn how to set up access controls a-la Github and Bitbucket for your own repositories. So you can do 'git clone git@yourwebsite.tld:project_name' as well as your own unlimited private repos!

Also https://github.com/gogits/gogs which I run on my VPS and though I still rely on GitHub first and foremost (because GitHub is way better), it's good to have.

Never had any problems with BitBucket over a few years. Using Mercurial though, which helps.

I use BitBucket and love it for all my single user projects.

This. Bitbucket all the way.

i'm actually using visual studio with checkouts from butbucket. but i started a new project (that depends on windows anyway) on VSO to check out.

honestly, i'd be really happy if my company ditched github enterprise to either of those.

... funniest typo I've had so far :)

bitbucket also supports free private repos.

I'm not suggesting you shouldn't try or use this option (I've always been a fan of most of Microsoft's dev tools), but I've been using bitbucket as my "side project" source code control system for free (incl. private repos) for years.

Nice, didn't know that. I'm a .NET guy though and have only used SVN and TFS at work, so now I can use TFS at home as well. Probably should learn Git with my next project...

> Probably should learn Git with my next project...

Do it. And I'm saying that as your fellow .net guy.

The only downside is that you will start hating TFS at work for being so God damn dinosaury afterwards ;)

git-tfs[0] is excellent. Amaze your co-workers by actually usefully merging between branches, and work without the dreaded check-out!

0: http://git-tfs.com/

I've looked at similar stuff before[1], but it broke under the immense pressure of our enormous branches. It was called git-tf and was java based.

This looks similar, but the following line made me want to give it a shot:

    git-tfs is designed to work outside of any existing TFS workspaces.

God I hate TFS workspaces. Archaic piece of shit.

[1] https://gittf.codeplex.com/

I would definitely move to Git if you have the choice. TFS is a dog compared to Git. And don't even get me started on the shambolic 'local workspace' in TFS, how it's possible to make local access slower than server access is beyond me.

TFS is fucking awful. And I do not say that lightly. It's really, really fucking awful. There's plenty of MS stuff i like, but TFS, no.

That you'd want to use it at home makes me question your sanity.

Git comes with Visual Studio since Visual Studio 2013, so it's a lot more seamless.

Though iirc git+ssh was broken... Not sure if it still is.

https://try.github.io/levels/1/challenges/1 Is a good quick 15 minute tutorial

Atlassian have some really nice Git tutorials with comparisons to the svn workflow.

https://www.atlassian.com/git/

From what I understand, most people at Microsoft use Git - not TFS. The true power of Git shows itself when working on huge projects with a lot of developers and release branches.

Actually most people use TFS at Microsoft. Some 61,777 Microsoft employees as of last month were using actively using TFS(VSO - The cloud offering of TFS).

Now the version control part of TFS is TFSVC and yes TFS does have the ability to host Git repos, but the number of Git repos at Microsoft is significantly, significantly smaller than then number of TFSVC based projects.

http://blogs.msdn.com/b/bharry/archive/2015/06/03/team-found...

Microsoft as a whole "gets" the need to move to better version control tools such as Git....but the larger products will take decades to move off of the internal version control tooling for example: Windows (Perforce\Product Depo), Office (Perforce\Product Depo), SQL Server (TFVC), etc.

Single User Git was the best thing I have done. I have backups and documentation.

Reply on news.ycombinator.com