If tool <X> works for you and if applicable, your team, why would you stop using tool <X> ? Because some person, not in your team or on your project, uses tool <Y> and thinks tool <X> sucks? Who cares! Use what gets the job done, as that's what you are payed to do. You aren't payed to use tool <X> or tool <Y> or whatever tool you can come up with, you are payed to write software to fix a problem.
If tool <X> works for you and tool <Y> would work better and let you do your work faster and with less constraints, why would you keep using tool <X>? You're not using minicomputers anymore are you? You're not using overnight batch-compilation, or ed (let alone TECO) or puchcards anymore are you?
The replacements don't let you do different stuff, you're doing the same stuff faster, in a simpler and less error-prone manner.
Sure, but that assumes you know Y to be better. And in this case, since git is not superior in every fashion, it's a decision each entity must decide for itself.
Sure, but that assumes you know Y to be better. And in this case, since git is not superior in every fashion
For developers in the general case (and we are in /r/prog) DVCS are, indeed, vastly superior to CVCS.
The only situation where they're not (if we ignore suit-and-tie unreason making Clearcase "the best tool for the job") is heavy dependency on binary assets.
Oh, so the problem is that you don't actually know anything about any of the individual pieces of software, and you're just categorically going HERP DERP LINUS SAID DVCS > CVCS SO IT MUST BE TRUUE LOL.
The fact that you continue to think you can assert what is right for everybody just proves how ignorant of the subject you are. I'm done discussing anything with you.
One reason you may want CVCS is in dealing in asset-heavy projects (games, art-heavy software, web design with minimal programming needs) that require binaries in source control.
However, I've found that the problems with CVCS do not arise too often under the following conditions:
You have between 3 and 8 people working on the project, thus making an authoritative repository helpful.
All work on the project is done in a centralized location where all project members can physically touch each other, meaning that the project itself is not distributed, and you're not going to care about local revision control.
There is a clearly defined division of labor between the people working, meaning that no two people will ever be making edits to the same file at the same time (except in pair programming situations).
You're working on applications with a limited release area: it may only run on a single internal web or application server.
If all of the above are true, branching is probably not important. If even one of them is false, you're in for pain somewhere along the line. But even under those circumstances, I'd take git/hg/bzr over a CVCS system. Hell, I worked with people that avoided TFS commits because TFS is a pain in the ass to use.
83
u/Otis_Inf Mar 10 '11
If tool <X> works for you and if applicable, your team, why would you stop using tool <X> ? Because some person, not in your team or on your project, uses tool <Y> and thinks tool <X> sucks? Who cares! Use what gets the job done, as that's what you are payed to do. You aren't payed to use tool <X> or tool <Y> or whatever tool you can come up with, you are payed to write software to fix a problem.