What’s wrong with Git? A conceptual design analysis (2016)

Re:What’s wrong with Git? A conceptual design analysis (2016) by dijit on Tuesday April 27, 2021 @06:11PM (#26962445)

Perforce for assets? Sure.

Perforce for code? It tries.. but, no thank you. Even if the client was good (it's really not, and will spin a CPU core when it detects a network hiccup) -- it still has a frustrating workflow paradigm, p4ignore is configured per-client, everything is read-only (leading to ugly context switches unless your editor directly integrates with p4) and the command line is so terrible that I think it was actually a joke that someone ran with.

No, perforce is not what you want, without even going into the "decentralised vs centralised" aspect of it.

[ Parent | on HN ]

Re:What’s wrong with Git? A conceptual design analysis (2016) by andromeduck on Tuesday April 27, 2021 @07:27PM (#26963376)

It's not p4 but Google3 + Hg CLI was way more fluent than I expected. I wish the third party portion were available as a service outside.

[ Parent | on HN ]

Re:What’s wrong with Git? A conceptual design analysis (2016) by dijit on Tuesday April 27, 2021 @07:29PM (#26963405)

Well, piper is "perforce that doesn't suck (and costs a heck of a lot less)"

I wish it were public.

[ Parent | on HN ]