• 0 Posts
  • 39 Comments
Joined 11 months ago
cake
Cake day: December 16th, 2023

help-circle











  • Active GuixSD user.

    Our application catalog is much smaller than many other distros simply because we don’t have the userbase large enough to surface the volunteers necessary to support it. So you will have to learn to write your own packages eventually

    That said, if you know your way around functional languages (in this case, scheme), it’s probably the easiest time I’ve ever had writing a package. Everything that goes into the script is known at the time the script is written, so weird extrinsic problems don’t really occur after you’ve written the package.

    Some stuff that you and the guix maintainers may not have the time to support will also get updated more slowly.

    Luckily flatpak exists, and is a godsend for the new wave of read-only (functional/ostree-based) OSs.

    Biggest appeal for me was having all my configuration in one place (and documented) so if I forget I did something in 6 months, it’s always staring at me in my home or system config file. You can accomplish the same thing by being diligent with say, script files, but it’s drop-dead easy to just maintain a system and home descriptor file and keep editing that.





  • The problem is that the Linux kernel is monolithic so introducing rust into it does have certain repercussions about downstream compatibility between modules.

    Right now the rust code in the kernel uses c bindings for some things and there’s a not-insignificant portion of C developers who both refuse to use rust and refuse to take responsibility if the code they write breaks something in the rust bindings.

    If it was pure C there would be no excuse as the standard for Linux development is that you don’t break downstream, but the current zeitgeist is that Rust being a different language means that the current C developers have no responsibility if their code refactoring now breaks the rust code.

    It’s a frankly ridiculous stance to take, considering the long history of Linux being very strict on not breaking downstream code.


  • Well part of what it does is grab your actual desktop background to use, and there’s a couple different ways to do that on Linux afaik

    Also I guess the file dialogs would open only to the wine prefix? My experience with wine applications and dialogs is mostly through bottles, so I’m not sure of the sandboxing…