@sharkfucker420 It’s a good thing “A Modest Proposal”[1] wasn’t titled “The Benefits of Cannibalism” because I guess people would have taken that at face value as well.
Large sheep the size of a small sheep! Late 20’s queer sysadmin, release engineer and programmer. Likes tea, DIY, and nerd stuff. Follow requests generally accepted but please have a filled out profile first!
@sharkfucker420 It’s a good thing “A Modest Proposal”[1] wasn’t titled “The Benefits of Cannibalism” because I guess people would have taken that at face value as well.
@HawlSera I do recognize that tomboys, buff women, etc are worth representing, (and we should push for their inclusion) but that’s not what I’m talking about - I mean people who look like “men” but use pronouns other than he/him.
@HawlSera @chloyster I mean, I absolutely know people who use she/her but present very masc, and vise-versa. They may be relatively uncommon, but so are trans people in general and we’re still worth representing. Not to mention non-binary people who have relatively binary gender presentation. Your experience is absolutely not universal.
@chloyster @alyaza I had no idea the series was developed by Humongous! That studio made so many good games that I’m nostalgic for.
@agressivelyPassive You should still clean your kitchen though, that’s my point.
@agressivelyPassive @technom That’s a self-fulfilling prophecy, IMO. Well-structured commit histories with clear descriptions can be a godsend for spelunking through old code and trying to work out why a change was made. That is the actual point, after all - the Linux kernel project, which is what git was originally built to manage, is fastidious about this. Most projects don’t need that level of hygiene, but they can still benefit from taking lessons from it.
To that end, sure, git can be arcane at the best of times and a lot of the tools aren’t strictly necessary, but they’re very useful for managing that history.
@FlyingSquid “Ok, then. That was always allowed!”