Perforce
Perforce
Posted Oct 21, 2009 19:21 UTC (Wed) by ceswiedler (guest, #24638)In reply to: Perforce by SLi
Parent article: KS2009: How Google uses Linux
People use Perforce because it works very well for centralized version control, and that's what a lot of companies need. It enforces user security, integrates with a lot of other software, can be backed up centrally, and has a lot of very good tools. On the other hand, it doesn't scale as well as DVCSs do, and can't be used offline.
Posted Oct 21, 2009 21:11 UTC (Wed)
by man_ls (guest, #15091)
[Link] (1 responses)
Posted Oct 31, 2009 4:55 UTC (Sat)
by Holmes1869 (guest, #42043)
[Link]
That being said, I feel that some of the git features will only ever be used by people that take source control seriously. The people I work with check-in code without commit messages, mistakenly commit files that they forgot they changed (or other random files that ended up in their sandbox), and don't ever perform a simple 'svn diff' (or Subclipse comparison) just to make sure they are checking in what they want. Do you think these people care that they can re-order or squash a commit to create a single pristine, neat, atomic commit to fix exactly one particular bug? Probably not unfortunately. I hope to one day work with people that do care.
Git is lightning fast (at least for code, I don't know for binaries), it's distributed and (surprise surprise) it's addictive! The cycle of 'commit, commit, commit, push when you're ready' is amazingly productive. I'm using it in my first project as single developer and I wouldn't change it for anything else I've used -- including cvs, svn, ClearCase, AccuRev and a few others too shitty to mention.
Git it
Git it