> If you are using Perforce as an enterprise system, $500 is peanuts. Perforce can get pricey.

i think it was $600/seat back when i paid attention (20+ years ago). don't remember if it was perpetual or annual.

> However, I continue to be amazed that Perforce survived Git. I assume its ability to handle large binaries has been what saved it.

yeah i think it lives on in games probably mostly through inertia. last i looked the company itself had shifted away from p4 classic to some git wrapper stuff.

i've never actually seen it but my understanding is that google's custom internal system (piper) basically is a reimplemented scalable p4+g4 wrapper.

i always thought the workspace mapping and workspace template model in p4 was pretty elegant, especially for things like embedded platforms where you could opt in and out various subtrees which made very large device trees/bsps more manageable.

also they were the first widely deployed vcs system that attempted to be efficient (server side indices for local tree state and communication with the server in deltas rather than forcing complete rescans for every operation that often involved talking to the server as each file was scanned)