You prefer:

     (add-after 'install 'remove-examples
       (lambda* (#:key outputs #:allow-other-keys)
         (with-directory-excursion
             (string-append (assoc-ref outputs "out") "/lib")
           (for-each delete-file
                     (list
                      "basic-server"
                      "helloworld"
                      "postcollector")))

over:

postInstall = ''
   rm  $out/lib/basic-server $out/lib/helloworld $out/lib/postcollector
''

?

The two main advantages of Guix are the language

I wouldn’t call that an advantage for the average person. Nix is far nicer to work with. Some Lispers might disagree, but I, for one, can’t exactly see the beauty in trying to turn Scheme into a configuration language with macros and hacks. Also Guix puts Scheme everywhere, things you can do with plain old Bash in Nix, you’ll have to all do in Scheme in Guix, so there is a much steeper learning curve.

You can manage multiple machines with a single Nix configuration git repository and modularize the configuration as much as you want. You can have a config with a desktop environment that you skip on servers, override individual variables for a specific host or do whatever you want. You can even remote deploy it all with a simple nixos-rebuild build --target-host "user@host" and it works across different architectures too (e.g. build on your fast x86 machine and deploy to a slow RaspberryPi).

I use bat sometimes, but how do you stop it from wrapping lines?

$ cat ~/.config/bat/config
--wrap=never