[–] 4 points 11 hours ago*

I think letting the others work out the kinks before making big investments makes sense. What is the benefit of being first vs. additional sales? Look at Microsoft with their OS LLM integration. They are backpeddling due to cost and user resistance. Their users can always use other general purpose LLMs.

  • source
  • [–] 7 points 2 weeks ago

    Leaving this here for anyone interested in why the grim reaper has a scythe.

    Wikipedia

    The scythe as an artistic symbol of death has deliberate agricultural associations since the medieval period due to the importance of farming and seasons. The tool symbolizes the removal of human souls from their bodies in huge numbers, with the analogy being to a farmer (reaper) cutting through large swaths of grain crops during harvest.

  • source
  • [–] 63 points 3 weeks ago (3 children)

    I'd just like to interject for a moment. What you're refering to as You, is in fact, Demodex/You, or as I've recently taken to calling it, Demodex plus You.

  • source
  • [–] 2 points 3 weeks ago

    Played this a few years ago. Worked great, but the Ai was a bit dumb at times. Since then, there's been a ton of improvements to the AI, so I'm sure it's in a much better place now.

    There's a lot of QoL improvements to the UI and usability. Would def play this over the original.

  • source
  •  

    What are some general recommendations to maintain a set of patches on top of a library distributed as a source tarball? Until now I've been adding the versions to a git repository by deleting previous files and adding the new files in a "upstream" branch, then merging that branch into the main branch which contains my patches. This turned into more work than I expected because they started moving files around and renaming in new releases.

    I should probably be rebasing instead of merging, but are there any other recommendations for this type of situation?

    view more: next ›