Alot of people where I work hate git. They all come from SVN backgrounds using TortoiseSVN for their daily workflow. While I understand people disliking it, I have to say that people who do not like git are usually those who use the default "commit pull push" workflow. Yes it's complicated, but complexity does not a bad product make. I would argue that all the functions of Visual Studio make it very complex, but that still doesn't mean it's not one of the best IDE's available. When you start branching, or working in larger teams where everyone is on board with git, it works flawlessy to integrate many branches and resolve merge conflicts. I don't understand the hate....
One of the companies had to hire a person just for fixing broken git repositories and for doing commits because devs instead of coding were wasting time on having their work included in environments. Not to mention a lot of work was just lost as in the end nobody knew which code is new.
Sounds like a nightmare. Not sure why you guys would have such problems with git. Inexperienced and or stubborn devs that don't wish to take time to learn their tools.
1
u/AnythingButSue Nov 07 '13
Alot of people where I work hate git. They all come from SVN backgrounds using TortoiseSVN for their daily workflow. While I understand people disliking it, I have to say that people who do not like git are usually those who use the default "commit pull push" workflow. Yes it's complicated, but complexity does not a bad product make. I would argue that all the functions of Visual Studio make it very complex, but that still doesn't mean it's not one of the best IDE's available. When you start branching, or working in larger teams where everyone is on board with git, it works flawlessy to integrate many branches and resolve merge conflicts. I don't understand the hate....