Chamomile 🐑

@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.

[1] https://en.m.wikipedia.org/wiki/A_Modest_Proposal

@P4ulin_Kbana @potentiallynotfelix fw = fuck with. It means they like it.

@AVincentInSpace @remington The Lemmy devs are infamously difficult to work with. They’ve repeatedly shown an unwillingness to even acknowledge the existence of the many problems that instance admins face. That has been a big driver in Beehaw’s decision to move platforms, not just because of a difference in political views, and they’ve been pretty open about discussing it. You’re way off-base.

@Templa Codidact seems promising in this space. They have a non-profit organization and run on an open-source (but not federated) platform: https://codidact.com/

@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.