Comment by retrocryptid
3 days ago
Oh man. I was just reminded of ClearCase and Perforce and sort of threw up a little in the back of my mouth. You young whipper-snappers who didn't have to use ClearCase and have only used hg or git don't know how bad it could be. When ClearCase was properly configured, it was fine. But having used it at IBM, DSCCC and Bell Canada, only IBM managed it properly. At DSCCC, we had 40 Sun workstations on a single thin-net segment, each of them trying to mount an NFS share from ClearCase. You had to get there at 6AM to be one of the first five people to log in because if you didn't it was unlikely you COULD even log in. I kept a copy of the part of the code I was working with on a tape and would go into the lab and restore it from tape, do some work, then back it up to tape at the end of the day (the lab machines were reformatted at midnight every day.)
But... yes... this is just using NFS locally to see what's already in GIT, which is perfectly find and as Julia says, allows you to appreciate the structure of the git repo. Ignore this old man yelling at clouds.
ClearCase was the main system at Altitude Software in Portugal, and at Nokia, eventually replaced by Subversion.
Yes, it was, is, quite complex and requires a dedicated team, however there are plenty of features that are still to be made available as easyly.
I loved my view configurations, there were some tricks we could do for mix and match what code to see, and the build caches to this day is still not as integrated as sharing object and library files was back then.
GE moved off Clearcase in 2019 because even IBM didn’t want to use or support it anymore. Wasn’t set up as bad as you had but wouldn’t describe it as pleasant. Lot of alias cheatsheets. Now we’re on perforce transitioning to git.
Oh nooooo.