|
|
|
|
|
|
by thibaut_barrere
5671 days ago
|
|
|
It's obsolete only for a small part of IT (us!), it's definitely not obsolete for them (and a lot of other shops). Three main reasons: - windows support is still far from brilliant for git - even a non-technical user can understand and use tortoisesvn in 2 hours - SVN revisions are really easy to understand Don't get me wrong, I'm using git in a lot of places (including my own projects), but most of my non-technical clients are on svn. EDIT: just so you know, I still know one company (a startup, mind you!) that uses CVS. |
|
|
It's not that bad, certainly not much worse than SVN itself on windows.
>- even a non-technical user can understand and use tortoisesvn in 2 hours
2 hours? A non-technical person can understand everything about e.g. Git that they're likely to need in less than that.
>- SVN revisions are really easy to understand
Not sure what you mean here. 1783. Is that somehow easier to understand than an equally meaningless hash key? At least in Git you could describe the version by the checkin text.
>but most of my non-technical clients are on svn
I think you're really doing them a disservice with this. As soon as they have any kind of accidental corruption I think you're going to be sorely missing Git's recovery capabilities and ability to mathmatically prove you're working with the version you think you're working with.