3 ms·

What alternative do you prefer?

by barbs 12y ago

bsder 12y ago
Mercurial.
- barbs 12y ago
  Thanks for replying to a question not asked to you, with an answer that doesn't explain your position at all.
  - jacquesm 12y ago
    Don't ask questions in an open forum if you aren't willing to accept with grace answers to your question from others, use email instead. Besides, his answer explained his position perfectly.
    - barbs 12y ago
      No it didn't, it was just one word! It gave no value to the discussion at all!
chx 12y ago
bzr. The CLI interface is much nicer and consistent. It has bound branches which is really useful useful when you are doing something small (see bsder comment above). You are not forced to use a staging area. There is no need to squash commits just to have a clean history instead you commit what you have and limit the depth of the log on view. Also, bzr is really easy to extend in Python. And so on and so on. The git command line interface is the exact opposite of user friendly: some commands have options that fundamentally change the operation so much so it should be a different command: git reset removes changes from the index leaving your files intact and if you do not have anything staged then does nothing. Now, git reset --hard simply throws away your changes. This does not end here: git reset 'HEAD^' will remove a commit. How mad is that, git reset operates on the staging area but git reset something operates on commits?? git checkout filename is almost completely unpredictable as it might get the file from the index if it exists there or from HEAD if not. There is no indication at all what happened. And so forth.
- barbs 12y ago
  Interesting, I've not ever seen a recommendation for bazaar over git or mercurial. I have heard that mercurial's CLI is a bit more sane than git, and I've also read that it's easier to extend in Python. How would you compare bazaar to mercurial? I've actually only ever used git for professional and personal development, but I think I'll want to play around with both mercurial and bazaar now. Git's CLI is definitely a bit of a PITA. I find this video summarises git's frustrations pretty well :) https://vimeo.com/60788996 https://vimeo.com/60788996.
  - chx 12y ago
    I will be ready to admit I haven't used mercurial much. But ... how does mercurial help the "small" use case?
  - ngoldbaum 12y ago
    Bazaar is basically unmaintained at this point. If you look on Launchpad, the trunk branch hasn't seen a commit since December 2014 [0]. There hasn't been a release since August 2013 [1]. Mercurial is very actively developed, with dozens of patches a month [2]. They also keep to a planned rolling release cycle [3] along with deep commitments about backward and forward compatibility [4]. New features like the experimental evolve extension [5] are also really cool. I use it for day-to-day work and find it incredibly useful for editing work-in-progress commits into nice self-contained patches. [0] https://code.launchpad.net/bzr/trunk https://code.launchpad.net/bzr/trunk [1] https://launchpad.net/bzr/ https://launchpad.net/bzr/ [2] http://selenic.com/pipermail/mercurial-devel/2015-March/thread.html http://selenic.com/pipermail/mercurial-devel/2015-March/thre... [3] http://mercurial.selenic.com/wiki/WhatsNew http://mercurial.selenic.com/wiki/WhatsNew [4] http://mercurial.selenic.com/wiki/CompatibilityRules http://mercurial.selenic.com/wiki/CompatibilityRules [5] http://mercurial.selenic.com/wiki/ChangesetEvolution http://mercurial.selenic.com/wiki/ChangesetEvolution
    - chx 12y ago
      Yes. git won, bzr is dead. As I said: I am aware and I switched to git because everyone else did. Just don't expect me to be happy about it.

What alternative do you prefer?

by barbs 12y ago

What alternative do you prefer?

bsder 12y ago

Mercurial.

barbs 12y ago
Thanks for replying to a question not asked to you, with an answer that doesn't explain your position at all.
- jacquesm 12y ago
  Don't ask questions in an open forum if you aren't willing to accept with grace answers to your question from others, use email instead. Besides, his answer explained his position perfectly.
  - barbs 12y ago
    No it didn't, it was just one word! It gave no value to the discussion at all!

chx 12y ago

bzr. The CLI interface is much nicer and consistent. It has bound branches which is really useful useful when you are doing something small (see bsder comment above). You are not forced to use a staging area. There is no need to squash commits just to have a clean history instead you commit what you have and limit the depth of the log on view. Also, bzr is really easy to extend in Python. And so on and so on. The git command line interface is the exact opposite of user friendly: some commands have options that fundamentally change the operation so much so it should be a different command: git reset removes changes from the index leaving your files intact and if you do not have anything staged then does nothing. Now, git reset --hard simply throws away your changes. This does not end here: git reset 'HEAD^' will remove a commit. How mad is that, git reset operates on the staging area but git reset something operates on commits?? git checkout filename is almost completely unpredictable as it might get the file from the index if it exists there or from HEAD if not. There is no indication at all what happened. And so forth.

barbs 12y ago
Interesting, I've not ever seen a recommendation for bazaar over git or mercurial. I have heard that mercurial's CLI is a bit more sane than git, and I've also read that it's easier to extend in Python. How would you compare bazaar to mercurial? I've actually only ever used git for professional and personal development, but I think I'll want to play around with both mercurial and bazaar now. Git's CLI is definitely a bit of a PITA. I find this video summarises git's frustrations pretty well :) https://vimeo.com/60788996 https://vimeo.com/60788996.
- chx 12y ago
  I will be ready to admit I haven't used mercurial much. But ... how does mercurial help the "small" use case?
- ngoldbaum 12y ago
  Bazaar is basically unmaintained at this point. If you look on Launchpad, the trunk branch hasn't seen a commit since December 2014 [0]. There hasn't been a release since August 2013 [1]. Mercurial is very actively developed, with dozens of patches a month [2]. They also keep to a planned rolling release cycle [3] along with deep commitments about backward and forward compatibility [4]. New features like the experimental evolve extension [5] are also really cool. I use it for day-to-day work and find it incredibly useful for editing work-in-progress commits into nice self-contained patches. [0] https://code.launchpad.net/bzr/trunk https://code.launchpad.net/bzr/trunk [1] https://launchpad.net/bzr/ https://launchpad.net/bzr/ [2] http://selenic.com/pipermail/mercurial-devel/2015-March/thread.html http://selenic.com/pipermail/mercurial-devel/2015-March/thre... [3] http://mercurial.selenic.com/wiki/WhatsNew http://mercurial.selenic.com/wiki/WhatsNew [4] http://mercurial.selenic.com/wiki/CompatibilityRules http://mercurial.selenic.com/wiki/CompatibilityRules [5] http://mercurial.selenic.com/wiki/ChangesetEvolution http://mercurial.selenic.com/wiki/ChangesetEvolution
  - chx 12y ago
    Yes. git won, bzr is dead. As I said: I am aware and I switched to git because everyone else did. Just don't expect me to be happy about it.