3 ms·
Hmm, that doens't sound bad. I don't remember (nor fully understood) why it was that complicated at google. At a wild guess it's ultimately connected to google
by cben 12y ago
Hmm, that doens't sound bad.
I don't remember (nor fully understood) why it was that complicated at google. At a wild guess it's ultimately connected to google's choice to keep all company code in a single humongous repo, which required a lot of later creativity to keep P4 from collapsing under the weight...
- stormbrew 12y agoI would think that the amount of data wouldn't be the thing that would make p4 fall over (it's pretty decent at that), but the number of users. P4, iirc, stores all client state server side, even to what files you're editing. So if you had to work around anything, it was probably that, and I can definitely see how that would break the ease of the workflow.