3 ms·

Which tool do you prefer the most?

by debacle 14y ago

Tloewald 14y ago
We assume ClearCase is the worst, right?
- igrekel 14y ago
  Assuming too much... People who conplain loudly about ClearCase most often never understood how it is supposed to work. Ok ok, you need an army of administrators to make it work but still far from being the worst. Sourcesafe?
  - raverbashing 14y ago
    "most often never understood how it is supposed to work" This is a BS argument. Yes, everybody got it wrong, Git is wrong, SVN is wrong, it's CCs broken model that's correct. " you need an army of administrators to make it work" Yes, let's sink an awful amount of money in a half-baked software that needs all kinds of 'helpers' to work properly. Personally I won't work in a company that uses CC anymore, and it's been only bliss since then. Sourcesafe is bad, but it's a different kind of bad. And it makes even CC look good.
  - Tloewald 14y ago
    I don't have any experience of knowledge of Sourcesafe, but it wasn't in the original list ;-)
silverbax88 14y ago
TFS for large scale enterprise, hands-down. But I don't recommend it for small shops. (Expensive, although I know it's free for shops with 5 devs or fewer) simply because code management is easy and you can build automated deployment without having to use anything else (you can script with PowerBuilder, Ant, whatever if you like, though). The issue I've found with that is it's not easy to find people who don't code for a living but understand scripting enough to build automated deployments. I'm also not crazy about TFS' visual displays of branches - ClearCase (which is god-awful in every other way) has the best visual display of code and branches. Mercurial for anything smaller or startup. Love it. The issue with Mercurial is that you'll need to determine how you want to do automated deploy builds, but the code management is great and using BitBucket + Hg I never have trouble seeing which code I'm working in or resolving conflicts. I actually think Mercurial has the second-best visual branching display.
- daok 14y ago
  >>TFS for large scale enterprise, hands-down. Real big enterprise cannot use TFS without being in a mess with merge. You always have to merge to a parent which require a lot of organisation. Also, it's not the fastest source control when the code base is over few gigs per branches. With over 50 developers/testers (in the same project) we had reach a bottleneck with TFS.

Which tool do you prefer the most?

by debacle 14y ago

Which tool do you prefer the most?

Tloewald 14y ago

We assume ClearCase is the worst, right?

igrekel 14y ago
Assuming too much... People who conplain loudly about ClearCase most often never understood how it is supposed to work. Ok ok, you need an army of administrators to make it work but still far from being the worst. Sourcesafe?
- raverbashing 14y ago
  "most often never understood how it is supposed to work" This is a BS argument. Yes, everybody got it wrong, Git is wrong, SVN is wrong, it's CCs broken model that's correct. " you need an army of administrators to make it work" Yes, let's sink an awful amount of money in a half-baked software that needs all kinds of 'helpers' to work properly. Personally I won't work in a company that uses CC anymore, and it's been only bliss since then. Sourcesafe is bad, but it's a different kind of bad. And it makes even CC look good.
- Tloewald 14y ago
  I don't have any experience of knowledge of Sourcesafe, but it wasn't in the original list ;-)

silverbax88 14y ago

TFS for large scale enterprise, hands-down. But I don't recommend it for small shops. (Expensive, although I know it's free for shops with 5 devs or fewer) simply because code management is easy and you can build automated deployment without having to use anything else (you can script with PowerBuilder, Ant, whatever if you like, though). The issue I've found with that is it's not easy to find people who don't code for a living but understand scripting enough to build automated deployments. I'm also not crazy about TFS' visual displays of branches - ClearCase (which is god-awful in every other way) has the best visual display of code and branches. Mercurial for anything smaller or startup. Love it. The issue with Mercurial is that you'll need to determine how you want to do automated deploy builds, but the code management is great and using BitBucket + Hg I never have trouble seeing which code I'm working in or resolving conflicts. I actually think Mercurial has the second-best visual branching display.

daok 14y ago
>>TFS for large scale enterprise, hands-down. Real big enterprise cannot use TFS without being in a mess with merge. You always have to merge to a parent which require a lot of organisation. Also, it's not the fastest source control when the code base is over few gigs per branches. With over 50 developers/testers (in the same project) we had reach a bottleneck with TFS.