Hacker News new | ask | show | jobs
by rondon2 4113 days ago
"Linus uses CVS at home". That was the best line.

In all seriousness, I don't tell new members of my team about the CLI. We use Visual Studio and the VS UI plugin only supports add,commit,push,pull,undo.

2 comments

> only supports add,commit,push,pull,undo.

It supports checkout too :). I've used it for some projects here and, honestly, for 99% of scenarios it works - for the 1% you can get someone who knows git to fix things up (instead of a junior doing a rebase on public history or something).

GitVS significantly lowers the barrier of entry for Git, which almost every other Git interface is embarrassingly dreadful at doing.

This is one thing that Microsoft does that almost everyone else misses. It's part of the "embrace, extend, exterminate" idea that they are accused of from time-to-time. To extend, Microsoft takes a complicated concept like Git and creates a simple facade for it. While everyone was fiddling with htaccess and whatnot, Microsoft had a simple IIS UI designed for everyone and the more advanced scripting interface if you needed it. Instead of makefiles I simply add files to a project. Instead of resolving conflicts between packages and chasing down obsolete libraries you just double-click setup.exe. Instead of a rookie "corrupting" your Git master with a rebase, you have them adding, committing, pushing, pulling, undoing and checking out.

If anyone were to see the lack of functionality in the GitVS as embarrassing they would most certainly be correct: it's embarrassment for Git itself.

I give it 4/5 stars due to the over-dramatization. 80% of the room leaving because they never ran a successful command seems far fetched.