I’m not an expert on btrfs, but I assume the inconsistencies come from deduplication, metadata, and maybe compression. I think some of them just count raw block storage, and some include the cost of metadata.

Traditional du assumes that each file takes up it’s full space on disk which isn’t always the case on btrfs. When using btrfs backed oci images, storage can easily appear multiple times higher.

I use btrfs filesystem usage /. I’m not sure that it is the “correct” way, but it works fairly well.

Slint has fairly decent docs and has worked fairly well for my small projects

I’ve gotten tired of weird regex stuff in awk, sed, and grep, so I’ve moved to perl -E for all but the most basic of things.

The main advantage of having a /home partition is that you can easily preserve it during reinstalls or during a distro hop. Reinstalls used to be more common in the past when some distros didn’t allow full distro upgrades without reinstalling. See this result which is still ranked #1 on duckduckgo

I personally use a @home btrfs subvolume which has most of the same advantages to me, and additionally allows @home and @root to share the same partition. It also allows me to use luks on everthing without bothering with lvm.

Are you sure your screen refresh rate is correct?

Zellij - a better way for a cli application to communicate with the terminal

Warp - a terminal emulater that integrates LLM completion natively

Fish - a shell that generates completions automatically from a man-page

They could be refering to the V programming language

I may be missing something, but the only machine learning focused api I know of are AMD’s ROCM, Nvidia’s CUDA, and now Intel’s oneAPI. I haven’t looked into Apple’s machine learning frameworks and I consider vulkan more of a general purpose api than a machine learning one.

Now there are 3 competing standards Edit: 6ish accually

Turing Complete Configuration

• more extensible
• tend to be heavier
• harder to provide detailed error messages
• more difficult for new users

Data Based Configuration

• easier to use
• easier to provide documentation
• lighter to embed
• more limited usecases

To enable the use of flakes, you have to use the ‘extra-expiremental-features flakes’ flag.

Edit: Apparently they are called ‘extra-expiremental-features’ not ‘extra-unstable-features’. Regardless the nix docs explicitly describe them as unstable here

https://nixos.org/manual/nix/unstable/contributing/experimental-features.html

Nixos

Pros

• Delarative Config
• largest package repos

Cons

• poor documentation
• cli and package management is in limbo with unstable flakes/cli

I’d consider dual-booting(windows+linux or linux+linux) or just installing a desktop environment. You can login to your wm and they can login to a full de

Congratulations and welcome. I use arch, btw

I use a shared boot partition all the time. I mount my EFI system partion on /efi. Then I bind mount /efi/$OSNAME to /boot in my fstab. Then I just manage my bootloader (typically systemd-boot or refind) manually. Any distros I install are installed in my encrypted btrfs partition within their respected subvolumes