5 ms·
Yes, when a command takes a couple seconds to perform, you don't consider doing it unless you have a really good reason. Classic hg branching came into differe
by dlsspy 17y ago
Yes, when a command takes a couple seconds to perform, you don't consider doing it unless you have a really good reason.
Classic hg branching came into different forms: 1) a tree clone and 2) the hg "branch" commands.
1 can be very slow on a large tree and can often require you reconfigure your tools to go look in a new place.
2 is permanent. Your code now forever references the name of a branch so you have to stop and think about whether it's really the right thing to do.
In either case, anything that requires me to stop and consider the cost of an operation makes the operation less valuable. Where that cost kicks in varies for people. Is it minutes? Seconds?
As a former perforce user, there were definitely plenty of things I wouldn't do there because they weren't instant. In git, I tend to make decisions based solely on my desired outcome.