• 1 Post
  • 100 Comments
Joined 2 years ago
cake
Cake day: December 16th, 2023

help-circle










  • As a guix user and package maintainer I’m ecstatic.

    I’m so proud of the community for rallying around the needs and pain points of everyone and making this decision. This reduces so many pain points for a guix user and will hopefully smooth out the package maintenance process a great deal. Email is simple but trying to do code change communication over it can be very complex and time-laborous.

    If you’re curious about functional packaging systems grab guix on your distro and give it a try!

    Special shout out to anyone burnt out on Nix lang. Come feel the warm embrace of Scheme’s parentheses. :)









  • WalnutLum@lemmy.mltoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    3 months ago

    guix and/or nix

    Both are functional package managers and manage dependency trees better than flatpak IMO (also the package description languages mean you can manipulate the package definitions at install time much easier)

    If you can’t find a package in guix/nix then it behooves you to use flatpak



  • The problem is that the road between creating a piece of software that does something well, and then creating simplification layers on top of it is typically much longer than just “edit a config file” and “here’s a readme”.

    You need extra documentation, config gating and workflow, warnings, UI/UX work etc.

    I know there are Linux elitists but kind of expecting that much extra work for what is still at it’s core mostly volunteer software seems like it’s own form of elitism.