It can be simplified with the use of runCommand:

{
  boot = {
    plymouth = {
      enable = true;
      theme = "breeze";
      logo =
        with pkgs;
        let
          src = fetchurl {
            url = "https://raw.githubusercontent.com/NixOS/nixos-artwork/refs/heads/master/logo/nix-snowflake-rainbow.svg";
            sha256 = "sha256-gMeJgiSSA5hFwtW3njZQAd4OHji6kbRCJKVoN6zsRbY=";
          };
        in
        runCommand "out.png" { } "${imagemagick}/bin/magick -background none -size 200x200 ${src} $out";
    };
  };
}

I think that you misunderstood my comment.

The video shows how SLI makes the frame pacing more inconsistent, which is a known issue when multiple GPUs work together to solve the same problem.

What I am talking about is more like Nvidia Optimus. This is a common technology on laptops, where the display is connected to the low power iGPU, while games can use the dedicated Nvidia chipset.

I don’t know about potential frame pacing issues on these technologies, and it seems like it was not addressed in the video either. However, I know that newer laptops have a switching chip that connects the display to the dedicated GPU, which, I think, aims on lowering the latency.

You can still use such GPU as an accelerator either for running AI, or for gaming. In either case, given that you workload is Vulkan-based on Linux, you can use vkdevicechooser.

Of course, you will need a second GPU (even the CPU’s integrated one) to connect your display(s).

VHS. No one will bother with it.

I trust no closed-source encryption mechanism. If I had to use any kind of cloud backup solution, I would first encrypt the files locally with a mechanism that I fully control.

I have been thinking of doing such thing to keep backups of my home Nextcloud server.

angel*