I’m a capitalist and this thread is giving me a hard-on

I basically stole your comment but made a worse version. On this note, though, there’s sometimes value in using words like “fix” or other kinds of tagging or consistent formatting in the sense that you can do a meta-analysis of the repo history to look at trends (like the ratio of fixes to feature work) over time.

Issue tracking software obviates that, somewhat, but having that info embedded in the repo history lets you go further and look at which files have the most fixes etc.

Existing tools out there sometimes do this exact thing, but it can be manually done as well

Knowing you fixed a bug is minimal information and usually covered by an issue reference in professional software development. I’d prefer to see the commit describing what the fix is actually doing to fix the bug.

You can admit you didn’t really give it much thought. I guess doubling down also works, maybe they’ll mod it into a VR GTA clone MMO for lulz

it’s an awareness tool, we’re talking about the game right now, people will play it on streams, dumb reactionaries will say stupid shit about it, and we’ll be talking about gun control bills all the while.

It’s like a PSA or political campaign ad, but interactive and intended to be viral.

It’s not trying to win game awards or start a video game franchise

Why would modders start with this basic game that lacks gunplay or NPCs to make a game where you play as a school shooter? The Unreal Engine empty project is closer to what you’d want as a starting point…

Worth noting that this is stored in the repository alongside the code changes and can be referenced in the future if someone is trying to understand that code or fix a bug in that code.

For large projects spanning long periods of time sometimes the best way to find a bug’s cause is to scour the projects history to find out which commit caused the bug to appear, and if that commit doesn’t have a good description you’re unnecessarily disadvantaged when trying to find out why it caused the problem or what assumptions were going into the original code.