Game programmer, designer, director; retired quadball player; antimeme; radical descriptivist; antilabel; Moose;

Working at Muse Games. Directed Embr, worked on Wildmender and Guns of Icarus, Making new secret stuffs

Opinions are everyone else's


Thew
@Thew

side note: I know none of us actually LIKE perforce and it has a million weird pain points, but I have to admit: In my entire career I have never ONCE had someone make a commit that broke the actual repository. Sure you can commit bad code that breaks the build/project, but never the VCS itself

Meanwhile it is a Routine Goddamn Occurrence for an entire git repo to get totally hosed because somebody accidentally Committed Wrong and now the whole system is unusable for everyone until the team's resident Git Priest spends an afternoon trying to unfuck it


Queso2469
@Queso2469

Git is best described as a good tool to build a version control system with.


You must log in to comment.

in reply to @Thew's post:

yeah p4 is in the "doesn't even list a price on their website" cost tier, so git is unfortunately the least-worst option for small budgets. I do like Mercurial a lot but yeah, had to eventually switch off of it because the tooling/ecosystem just isn't there

I am not sure I've ever experienced git breaking in such a way that it's everyone's problem instead of just mine

which uh. I do break mine all the time in various ways but I'm wondering what landmine I've only been accidentally avoiding

how do you commit wrong?

Here's a great one: commit two files that differ by case (linux) and clone them on a case-insensitive file system (windows/mac) OR change the casing and commit with the new casing on the case-insensitive system and try to clone on linux.