4 ms·
Of course, a really industrial-strength FizzBuzz would be in an SVN repo.
by portlander12345 14y ago
Of course, a really industrial-strength FizzBuzz would be in an SVN repo.
- packetslave 14y agoHa! You think any enterprise IT shop is going to trust an open-source product like Subversion with their mission-critical source code? It would be in Perforce or MS Team Foundation Server.
- at-fates-hands 14y agoSometimes they don't have a say. I've worked with several large fortune 500 companies who use SVN, regardless of how much the IT Department objected to it.
- jlgreco 14y agoEh, Perforce is too pleasant if we are really embracing enterprise; makes it too easy to do sensible things like use a git client. No, it has got to be SVN for maximum pain.
- steveklabnik 14y agoIf you think SVN is 'maximum pain' then you haven't tried out the full array of actually bad VCSes. SVN is fine, if a little outdated-feeling.
- kyllo 14y agoThree words: Microsoft Visual SourceSafe.
- jlgreco 14y agoBesides the "modern" VCS's, I've used SVN, CVS, Perforce, and done both manual patch management and patch management with Quilt. I am sure there are some VCSes out there I would hate more than SVN if I used them, SourceSafe I'm sure, but I would honestly use any of those others I just listed before SVN again. Yes, I consider SVN to be a devolution of CVS.
- skeletonjelly 14y agoThe merge tool (p4merge) is a dream, I shoehorn it into any VCS I use including TFS.
- MBlume 14y agoYou can use a git client with SVN pretty easily. Git is a far better SVN client than SVN is.