Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Rev

Well, maybe the biggest issue with ClearCase is that it is slow as molasses. So if the process is complicated (and there may be good reason for that), switching to something faster would improve it.
– Jan Hudec
Commented Aug 6, 2014 at 7:33
1

@JanHudec I recall Clearcase... it wasn't that slow where I worked but maybe its one of those products where the repo gets put on a server in a distant corporate datacentre surrounded by many layers of security and routing. I think the OP would have a better chance with SVN or TFS than git, but its not what he's set his heart on.
– gbjbaanb
Commented Aug 6, 2014 at 7:45
3

ClearCase is basically a network filesystem with versioning. So network bandwith and especially latency matter a lot to it. With local replica, most operations were bearable (but still a lot slower than in git, which is designed for speed), but some operations were horrible. The worst I did was labelling all files for release, which took 15 minutes and it was not an exceptionally huge project.
– Jan Hudec
Commented Aug 6, 2014 at 7:56
1

+1 for pointing out that it's a "people" problem rather than a technology problem.
– kdgregory
Commented Aug 6, 2014 at 11:49
1

The biggest nightmare I had with clearcase was that, like CVS, it only versioned at the individual file level; meaning merge problems/etc would result in the newest version in CC to become a broken build and the inability to roll an entire codebase back to an arbitrary date/time. Using the option to do a local view instead of a virtual network drive greatly reduced pain from IO latency.
– Dan Is Fiddling By Firelight
Commented Aug 6, 2014 at 14:15

| Show 3 more comments

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>

formatting help »
answering help »