Skip Navigation
spectrwm Tutorial & Review
  • Here's a prediction: not even fedora will drop it by 2027.

    Wayland still doesn't work for a lot of people, and the ecosystem is nowhere near mature enough. I doubt enterprise distros will consider dropping xorg until their users can actually work on Wayland.

  • spectrwm Tutorial & Review
  • IMO too much "Tutorial", not enough Review. For example:

    The spectrwm workflow is unique. It took me awhile to become acquainted with the standard flow and gain comfort in using it. I did have to bend, fold, and spindle the environment a bit

    You haven't written a single word on how it's different from any tiling manager, nor what and why you changed.

    Generally the article feels like the first comment in unixporn, where you list out your relevant dotfiles. The only extra information is that you like it, and a list of dependencies for your config.

  • New to Linux? Ubuntu Isn’t Your Only Option
  • Tumbleweed is recommended often here.

    I occasionally try out Opensuse since like 2007, but I always find the alternatives better. Why Tumbleweed over Arch, why Leap over Fedora/Debian, why suse over RHEL?

  • Introducing Fedora Atomic Desktops - Fedora Magazine
  • This shows something else. The traditional languages are all more common than Rust.

    It's a survey from 2019, but in those rust is traditionally the favourite language nobody uses professionally.

    I suppose Go could be a good competitor, and I read a thread comparing C=Go, C++=Rust.

    Go's syintax is C inspired, but it's not made to replace it, nor do they compete in the same space.

    Look at zig instead of you're interested in that.

    I am interested in a discussion about that, as I would like to learn one of these languages

    Skip rust unless you have years to get good at it.

  • Are there any immutable distros meant for NAS systems or home servers?
  • If you're running unstable system packages, immutability won't really save your stability.

    So don't complicate it, and just use Debian with nix and home-manager. That way you have a stable base, and you can create a list of bleeding edge packages that should be installed. In any case it should be essentially only docker + whatever can't be dockerised.

  • [Fedora 39] Why does Discover say there's updates while `dnf` say there's none? Also, why does Discover need to reboot to install said updates?
  • AFAIK no distro forces you to reboot, but they all require it for some updates to take effect. You can't reload the kernel while the system is running.

    Fedora just makes that clearer to the user by only installing those updates when they're going to be active - after a reboot. I think it also blocks new system updates until the current set is completely finished.

    You can disable offline updates in the system settings, but I think they're a good idea, especially for the average user.

  • Considering Starting Linux
  • Sudo apt... is not the problem. Home-manager and a list of packages are so much better and easier to manage. That's why I'm currently running nix on top of Debian.

    The problems start when you want to modify something, or when you want to use tools that expect fhs complience. Then you run into a skill mountain and discover that the documentation is not great.

    At least that's my experience with guixos and nix. I haven't tried nixos, and if I do, it'll be only to generate docker images and such.

    For a workstation, in most cases, there are simply not enough benefits to deal with the bs that comes with a declarative os.

  • How do you manage your packages with Nix?
  • That’s a really hacky method and should not be in the manual tbh.

    That's why I'm asking, it seemed really odd.

    home-manager

    Thanks, this makes a lot more sense. Any good resources besides the wiki? Is there a way to break down home.packages into smaller chunks for modularity?

    As for flakes: No, you don’t require them to do any of this. They solve an entirely different problem.

    So they're just to ensure reproducibility?

  • How do you manage your packages with Nix?

    Idea: Debian + Nix == stable and funky fresh

    I first came across Declarative Package Management in the manual. So I started making these packages based on it.

    The install works (nix-env -iA nixpkgs.my-emacs), but nix-env -u doesn't update changes (adding and removing packages from the paths). Do I need to reinstall my- packages to get updates as well? Does nix-env -u update package definitions (apt update)?

    After that I came across zero-to-nix. This approach wasn't mentioned at all in the quick start, and I came across comments that people shouldn't use nix-env anymore. Should I create flakes instead of packages, and export their paths to have them available globally?

    How do you use Nix to manage your packages? Do you have any examples?

    nix-env/nix profile/home-manager?

    5
    Just got a 200 dollar ticket for... "Running a red light'
  • Like, okay, even if I BLATANTLY ran it I can't even justify 200 fucking dollars for it.

    In my third world country that would cost you at least twice as much, and you'd also lose your licence for at least 3 months.

    But on the other hand the traffic cams won't record you unless all 4 of your wheels were in front of the traffic lights when they turned red.

  • InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)DR
    drndramrndra @lemmygrad.ml
    Posts 1
    Comments 65