4 ms·
It lends itself to a workflow where sometimes, a user checks out a file, and forgets to unlock it. Or goes on vacation. Then you have to forcibly check out the
by ams6110 12y ago
It lends itself to a workflow where sometimes, a user checks out a file, and forgets to unlock it. Or goes on vacation. Then you have to forcibly check out the file your coworker locked to get work done. And when he has to merge his changes with yours again, it’s a gigantic hassle.
This exactly describes web development on the Microsoft stack using Visual Source Safe. I don't know if that product exists anymore or still works the same way but the frustration with it is what drove the popularity of Subversion and then later Git.
- BugBrother 12y agoYou were probably too Microsoft specific in your work environment. CVS is older than most(?) HN posters and had no locking problem. So your pain was not necessary. :-( (The wikipedia says VSS was bought 1995, so the original product might be older?)
- wiml 12y agoCVS was developed in the '80s specifically to get around the locking problem that locking (non-concurrent — that's what the C in CVS is) version control systems had.
- gumby 12y agoAh, ams6110, I feel your pain, but you have not encountered true agony until you have been subjected to... Perforce (aka p4). It feels like the p4 designers WANTED software development to be harder. Perhaps they recruit developers exclusively from the pool of former TSA agents.
- philwelch 12y agoPerforce was fine compared to ClearCase.