Chamomile 🐑 @ANE 2026

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!

  • 0 Posts
  • 17 Comments
Joined 3 years ago
cake
Cake day: December 4th, 2022

help-circle

  • @Kolanaki @t3rmit3 The linked article is using “casual” to refer to a number of different traits - competitiveness is one of them, but also how demanding they are for your time and attention. Casual was probably the wrong word to choose, since it already has a different meaning for most gamers, but the thesis is more about the return of low-stakes FPS games that you can pick up here and there to goof off without being milked for every minute and dollar you can spare.

    An old guard of life-consuming live-service games remains a vibrant and popular part of this genre, but they’re once again sharing the space with—and even adopting the attributes of—a more casual breed. Games that don’t mind if you only play them once in a while. Games that let you make your own fun, encourage cooperation, or earn our respect by not bombarding us with ads.


  • @EldritchFeminity @infinitesunrise I’m not sure if it’s organized, but it does describe a specific school of thought that isn’t just “I don’t personally want to have kids.” Antinatalists generally believe that it’s unethical for anyone to reproduce. The core argument is usually that since you can’t consent to being born, you can’t ethically impose it on someone against their will. It tends to go hand-in-hand with misanthropic ideas such as that humans are destructive to the planet/fundamentally cruel or that life in general just sucks. Ultimately, the thesis is that humans should extinct ourselves. Given the current state of the world, it’s gained some traction amongst groups of people trapped deep in despair right now. (Which, let’s be real - there are a lot of on Lemmy)















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