5 ms·

Although GitHub offers a lot of features and generally makes Git tolerable, I’ll be pretty happy when Git gets supplanted by something else more popular and hop

by bmitc 4y ago

Although GitHub offers a lot of features and generally makes Git tolerable, I’ll be pretty happy when Git gets supplanted by something else more popular and hopefully better. The latter should not be hard to do. As someone who cut my teeth on Perforce, I’m still learning the ins and outs of Git and generally actively avoid Git features. Whereas with Perforce, I was writing custom applications using its API and powerful workspace concept in just a couple years. Perforce is just easier to understand, easier to customize, great visualization tools, and has more sane names for things.

sausagefeet 4y ago
I use Mercurial and hg-git, which is a two-way interface between mercurial and git, and except for a few situations (tags, for example) it is, IMO, a vastly superior client to git. I think a possible step forward would be to just accept git as an underlying file format and build clients that are not insane on top of it. Maybe we could move off the file format later.
- bmitc 4y ago
  Plastic SCM has some Git interfacing, but I’m unsure of the details. I like some of their other solutions as well, namely semantic versioning. https://docs.plasticscm.com/gitsync/plastic-scm-version-control-gitsync-guide https://docs.plasticscm.com/gitsync/plastic-scm-version-cont...
- arxanas 4y ago
  https://github.com/martinvonz/jj https://github.com/martinvonz/jj and http://sapling-scm.com/ http://sapling-scm.com/ are good steps in this direction!
unmole 4y ago
Heh. I picked up git in college because I wanted to hack on the Linux kernel. Once I grokked git's simple data model, I have never run into problems with it. On the other hand, I've had to use Perforce professionally and I find it unbearable. It lacks features and everything is just convoluted and ridiculously slow in comparison. Thankfully I can avoid having to deal with Perforce using a git wrapper.
- bmitc 4y ago
  Perforce has several features that Git doesn't have. > ridiculously slow in comparison That can’t true. Perforce is definitely much faster, especially with files that aren’t just small text files. One of my biggest complaints of Git is how slow it is. There’s a reason why game studios use Perforce or Plastic SCM.
  - doix 4y ago
    It makes different trade-offs. Perforce is much better at dealing with large binary files, git isn't good at that. There's 'git lfs', but I have no experience using it, so I can't comment. But if you're just dealing with text files, git is much faster in many cases compared to perforce. Switching/creating branches in git is instant, it can take a while in perforce. Doing a 'git status' is instant, 'p4 status' can take minutes to return in a large repo with many files.
  - unmole 4y ago
    Perforce clients needs to talk to the server for everything. Even opening a file for editing! It's not hard to see why it can be horribly slow. On the other hand most git operations are local and are blazingly fast. I'm not a game developer: Text files are all I care about.

by bmitc 4y ago

sausagefeet 4y ago

I use Mercurial and hg-git, which is a two-way interface between mercurial and git, and except for a few situations (tags, for example) it is, IMO, a vastly superior client to git. I think a possible step forward would be to just accept git as an underlying file format and build clients that are not insane on top of it. Maybe we could move off the file format later.

bmitc 4y ago
Plastic SCM has some Git interfacing, but I’m unsure of the details. I like some of their other solutions as well, namely semantic versioning. https://docs.plasticscm.com/gitsync/plastic-scm-version-control-gitsync-guide https://docs.plasticscm.com/gitsync/plastic-scm-version-cont...
arxanas 4y ago
https://github.com/martinvonz/jj https://github.com/martinvonz/jj and http://sapling-scm.com/ http://sapling-scm.com/ are good steps in this direction!

unmole 4y ago

Heh. I picked up git in college because I wanted to hack on the Linux kernel. Once I grokked git's simple data model, I have never run into problems with it. On the other hand, I've had to use Perforce professionally and I find it unbearable. It lacks features and everything is just convoluted and ridiculously slow in comparison. Thankfully I can avoid having to deal with Perforce using a git wrapper.

bmitc 4y ago
Perforce has several features that Git doesn't have. > ridiculously slow in comparison That can’t true. Perforce is definitely much faster, especially with files that aren’t just small text files. One of my biggest complaints of Git is how slow it is. There’s a reason why game studios use Perforce or Plastic SCM.
- doix 4y ago
  It makes different trade-offs. Perforce is much better at dealing with large binary files, git isn't good at that. There's 'git lfs', but I have no experience using it, so I can't comment. But if you're just dealing with text files, git is much faster in many cases compared to perforce. Switching/creating branches in git is instant, it can take a while in perforce. Doing a 'git status' is instant, 'p4 status' can take minutes to return in a large repo with many files.
- unmole 4y ago
  Perforce clients needs to talk to the server for everything. Even opening a file for editing! It's not hard to see why it can be horribly slow. On the other hand most git operations are local and are blazingly fast. I'm not a game developer: Text files are all I care about.