3 ms·
we just started a new project and we tried out git briefly. our prob with git is it supports ssh auth only (not HTTP Auth), which is retarded. makes setting up
by ohhmaagawd 18y ago
we just started a new project and we tried out git briefly.
our prob with git is it supports ssh auth only (not HTTP Auth), which is retarded. makes setting up new users a pain. and leading non-techies thru setting it up is quite a challenge.
the other major prob is lack of windows support.
the people coding git clearly don't care about average joe users, just unix geeks.
don't forget, there are a lot of people who use source control that have never opened a command line in their life (like designers, doc people).
Because of these issues we had to switch to subversion....
- epall 18y agoAnd Subversion is perfectly appropriate for your uses! TortoiseSVN is a snap to use (and it's not the only great svn GUI out there), and Subversion seems to make sense to people. The only reason I see to use git is if you're trying to keep a bunch of developers who are running off in different directions to maintain a somewhat coherent codebase. Or if developers want their own playground. Even then, though, I worked at a company that used centralized Subversion, but almost every developer used git-svn locally. Different tools for different applications!