4 ms·

I'd love to read a post where someone decided SVN is superior for their purpose, and their stance is defensible. I can't think of any reasonable use cases.

eli 16y ago
I'm not personally a big SVN defender/apologist, but I'll bite. Imagine you're on a small team developing closed source software. Like many people, you already have SVN, your team already knows SVN, it's already integrated into build system and you're using Trac for ticketing. Based just on that, I would absolutely keep using SVN instead of transitioning to Git. Perhaps you disagree, but I hope you'll at least concede that's a reasonable position.
- loup-vaillant 16y ago
  Of course transitions always cost something. For instance, C++ is the best when all your developers know C++ and have to extend a C++ code base. This examples are short term, and don't answer the question "is the new tool eventually better than the old one"? If so, consider switching costs. If not, don't even bother. So, a better example in the svn vs git matchup would be the handling of locks for binary files. Assuming of course you can't fix it yourself.
- dustingetz 16y ago
  well obviously, but the point is in a vaccuum, git as a tool appears to be superior in every way that matters.
  - mistermann 16y ago
    Most people neither live nor work in a vacuum. You come from the "ya, well..." camp it would seem? Supremely confident that your choices are the correct way to do things, but when someone points out a valid difference, your answer begins with "Ya, well...". I see this all the time from brash young superstars.
    - dustingetz 16y ago
      ya, well, factors external to the merits of the two tools is irrelevant to the question I intended to pose. My question could have been worded better, sorry for the confusion. loup-vaillant's explanation is clearer. ;)

4 ms·

I'd love to read a post where someone decided SVN is superior for their purpose, and their stance is defensible. I can't think of any reasonable use cases.

by dustingetz 16y ago

eli 16y ago
I'm not personally a big SVN defender/apologist, but I'll bite. Imagine you're on a small team developing closed source software. Like many people, you already have SVN, your team already knows SVN, it's already integrated into build system and you're using Trac for ticketing. Based just on that, I would absolutely keep using SVN instead of transitioning to Git. Perhaps you disagree, but I hope you'll at least concede that's a reasonable position.
- loup-vaillant 16y ago
  Of course transitions always cost something. For instance, C++ is the best when all your developers know C++ and have to extend a C++ code base. This examples are short term, and don't answer the question "is the new tool eventually better than the old one"? If so, consider switching costs. If not, don't even bother. So, a better example in the svn vs git matchup would be the handling of locks for binary files. Assuming of course you can't fix it yourself.
- dustingetz 16y ago
  well obviously, but the point is in a vaccuum, git as a tool appears to be superior in every way that matters.
  - mistermann 16y ago
    Most people neither live nor work in a vacuum. You come from the "ya, well..." camp it would seem? Supremely confident that your choices are the correct way to do things, but when someone points out a valid difference, your answer begins with "Ya, well...". I see this all the time from brash young superstars.
    - dustingetz 16y ago
      ya, well, factors external to the merits of the two tools is irrelevant to the question I intended to pose. My question could have been worded better, sorry for the confusion. loup-vaillant's explanation is clearer. ;)