• 2 Posts
  • 48 Comments
Joined 29 days ago
cake
Cake day: September 27th, 2026

help-circle












  • If you want a good first Linux experience, stick with anything Ubuntu-/Debian-based; they are

    • stable workhorses, i.e. they don’t break on you as easily as rolling release distros like CachyOS.
    • wildly popular, i.e. you’ll find plenty of resources to help you get started (although, to be fair, the Arch wiki is also ridiculously detailed).

    Whatever you do, steer clear of immutable distros like Bazzite for now. As cool as the concept is (I run Bazzite on my gaming machine) - as soon as you do something “non-standard” (and modding your Minecraft .jar with Optifine already qualifies as such), you’ll have to fiddle with the terminal and distrobox containers, both of which will be alien concepts for you at the start and may be top much to make it a good first impression.



  • Grimmory sounds like a new kid on the block, and indeed, it is. I’ve looked into it, and here’s what I’ve come up with:

    • initial commit: March 2026 --> very young project, blazed through 24 releases already
    • 165 contributors, but upon closer inspection, it relies on only two frequent contributors --> if they lose interest, the project might fall dormant or die entirely
    • as per its AI policy, the project embraces AI as a tool, but expects contributors to understand what they’re committing, and reserves the right to throw out blatantly vibecoded contributions. --> Whether two people can actually enforce this policy when getting firehosed with AI contributions remains to be seen.

    With all that in mind, I think I’ll give this project a pass for now. Like you said, it’s some work that goes into curating a library and making sure the metadata is correct, and if that locks me into a project that may or may not exist several months or years from now, I’ll probably stick to one of the more established projects with a higher likelihood of long-term maintenance.


  • Feel free to elaborate. ;) I don’t mind ditching folders. The question is: how do I get at said metadata with the least amount of manual effort, how do I make sure that it’s accurate (sifting through thousands of files is not fun), and how is the metadata stored - particularly so that does not lock me into one application that can only understand its own metadata scheme, and once it dies or I want to switch to a different one, I lose all the work I’ve put into curating my collection. That’s why I was considering folders as an option: they are a software-agnostic way of organising my library.