5 ms·
Why only Google and Facebook engineers? I use both Mercurial and Git, and honestly, they aren't that different. Unless you're doing something very specific I d
by mrweasel 12y ago
Why only Google and Facebook engineers?
I use both Mercurial and Git, and honestly, they aren't that different. Unless you're doing something very specific I don't see why you would choose one over the other.
- pdw 12y agoI don't know about Google, but I believe Facebook keeps all of its code in one gigantic Mercurial repository.
- jordigh 12y agoNot exactly "all", but certainly the mother load.
- digitalsushi 12y agoMother lode, the central, most valuable vein of buried gold.
- jordigh 12y agoOh, thanks! I'll let my original spelling stand as a testament to my ignorance. :-)
- thanksgiving 12y agoI've never used mercurial outside of TortoiseHg. In fact, the only time I've used mercurial is when I was attempting to build Firefox from source before I realized that they do a git mirror thing so you don't have to touch mercurial at all. I don't know much about mercurial. I use git because somebody said it is easier to rewrite history in git.
- Fenume 12y agoWhy would you rewrite history? Don't be ashamed.
- allersj 12y agoFor me, I tend to commit frequently, sort of like my obsession with constantly hitting CTRL-S while working in an IDE. Before I push my changes I like to squash the commits into more cohesive commits. If anything, I think it makes it easier on my colleagues for code review.
- jordigh 12y agoI do the same in hg. I do `hg amend` all the time to keep adding changes to my commit. At the end I may selectively undo some changes with `hg uncommit --interactive` or `hg uncommit --all` and redo the whole thing piecemeal with `hg commit --interactive` in order to slowly split up my work into several commits. Evolve makes it really easy to keep (and ignore!) a meta-history of all of my editions, with a clear lineage of which new commit replaced which prior commit. I may also rebase my work onto the latest head at the end (not to be confused with git HEAD). And all of this with a very nice interface. It's always --interactive, not sometimes --patch and sometimes --interactive.
- allersj 12y agoThanks, that is useful to know. Mercurial was my first DCVS and I loved using it, but I only touched on the basic features. I stopped using it when I switched jobs and to become proficient with git. I'll have to give it another try with one of my side projects.
- limeyx 12y agoThats not the same kind of rewriting history because its local to you and hasn't yet been pushed out to others. Git allows you to push commits to other people and then rewrite history, which is different
- 12y ago
- dcuthbertson 12y agoI don't believe the ability to rewrite history is a good idea. One of the reasons I like Fossil-SCM is that you can't rewrite history.
- voidr 12y ago> Subversion uses a centralized revision control model. Ben Collins-Sussman, one of the designers of Subversion, believes a centralised model would help prevent "insecure programmers" from hiding their work from other team members. source: http://en.wikipedia.org/wiki/Apache_Subversion#Limitations_and_problems http://en.wikipedia.org/wiki/Apache_Subversion#Limitations_a... Sounds like you should be using Subversion then. Do you understand how history rewriting works in git? do you understand why it's there? do you understand why people use it? Personal beliefs don't advance computing, hard facts do.
- durin42 12y agoNote that Ben (a personal friend) has been an enthusiastic user of Mercurial for several (4? 5?) years, and is pretty happy with it. He was even using hgsubversion for a while I think. Note that there's a lot of social problems around DVCS, and the thing Ben worried about is still a _real problem_. I get potential contributors showing up with months of work, and it's an enormous pain in the ass (both for them to rewrite and for me to beg them to work with me) when they did something architecturally unacceptable early in the process that a simple 2 minute review could have caught.
- krupan 12y agoBut would the insecure people have done that work at all if they knew they would be forced to commit it publicly? Maybe so, but would it all be one huge commit to svn instead of maybe a string of more concise commits to git or mercurial? I just envision someone insecure (like I feel at times) saying, well, I'll just clone this and play around on my own machine. Then after making some commits and building up courage, saying, OK, I'll try and go public with this. With centralized VCS that seems less likely to me. The insecure programmer just won't even try. I don't know, it's probably different for different people.