4/02    We use Perforce at work for revision control. It seems to work okay.
        Lately, a lot of the newer developers are saying that Perforce
        sucks and we should switch to Mercurial or Git. I have done some
        searching on the Internet and some others have this opinion. Added
        advantage is that Mercurial and Git are free. However, there would
        be some work to switch for the sysadmins and the developers.
        Is it worth it or do people just like what's shiny?
        \_ I *love* git but there are good reasons to use Perforce. Do they hold
           for you? http://stevehanov.ca/blog/index.php?id=50
        \_ I *love* git but there are good reasons to use Perforce. Do they
           hold for you? http://stevehanov.ca/blog/index.php?id=50
           \_ That post pretty much describes my experiences with git and p4.
              Unlike the author, I do use the distributed stuff in git (it's
              nice to have a local repository when you're working from home),
              but everything else is right on.
           \_ We're moving from Perforce to Git. Too many branches and pushing
              code around is painful. Idea is to properly componentize the platform
              and apps, and have 1 repo per jar, stored our GitHub-FI. Let maven
              download the dependencies and do the build locally. We'll see...
              code around is painful. Idea is to properly componentize the
              platform and apps, and have 1 repo per jar, stored our
              GitHub-FI. Let maven download the dependencies and do the build
              locally. We'll see...
        \_ These "new" developers want the latest and greatest. Hint. It's
           not about the language or the revision control system. It's how
           you use them. There are 10000s of ways to use Git. What is the
           convention you guys agreed on? That is more important that anything
           else. What happens if architect A wants to use convention A and
           another architect insists on using convention B and they're
           incompatible and you end up with a massively distributed unmergeable
           monster and end up bifurcating the code base? You're FUCKED!!!
           Another thing: having a code-review system is much more important
           than the revision control system. If you don't know what that is
           or understand why that is more important than language/system/platform
           then you should not be in a position to make this type of decision.
           What is your position in the company and are you in the position
           to make this type of decision?
           or understand why that is more important than language/system/
           platform then you should not be in a position to make this type of
           decision. What is your position in the company and are you in the
           position to make this type of decision?