Comment by rjsw
7 hours ago
People complained about having to use ClearCase back then, it wasn't just the price that was wrong with it.
7 hours ago
People complained about having to use ClearCase back then, it wasn't just the price that was wrong with it.
I helped swap a mess of ClearCase & Subversion over to git (early 2010s). What a fucking cursed piece of software!
Will admit it got exactly one thing right, which could absolutely justify everything else (including the price) for a long time: Software Bill of Materials, which is non negotiable in a lot of more serious/heavily regulated development contexts
That still didn't excuse the hacked together pile of ruby scripts our QA lead maintained, each one designed to unfuck a specific weird thing clearcase did. Once everything was on git, they just wrote another script that grabbed a bunch of tags from git and shoved them into clearcase to spit out the bom.
My first programming job was an internal line of business application at a mortgage vending company. There was an uncomfortable amount of time wasted waiting for someone to do something in ClearCase so I could commit. I've turned down interviews solely on the basis that I would be using that dumpster fire of lost productivity and UX from hell.
> Software Bill of Materials
Yet another thing that came from PRIDE, despite that PRIDE itself is little known in today's software industry.
The author praises the enterprise version vs. the more simpler one. Having had the pleasure coordinating one clearcase site in a very large distributed setup with significant replication traffic and windows and unix clients: It was an unstable mess.