Regarding snapshots, I use a setup, where at the root of the btrfs partition I have the subvolumes “rootfs”, “home”, and a directory “snapshots”. I can boot into a snapshot by changing the mount options for the rootfs in the kernel command line, e.g.setting subvol=snapshots/rootfs-yyyy-mm-dd.

The only difference between a snapshot and a regular subvolume is that snapshots are readonly by default, you can keep a writable copy of a snapshot beside it for recovery purposes, if you need it. As long as nothing is written in it, it shouldn’t use any significant extra space.

I don’t think working overtime has much to do with WFH vs office for most people. We have a lot more WFH here since covid, and the only people I know that work a lot of overtime already did that before WFH was introduced.

For me, WFH means an hour more of free time, as I don’t have to spend it in traffic on my way from and to work.

…and all I hear is: “this stuff isn’t ready yet” and “I’m going to be starring at Unicode glyphs the next time I have to tinker outside of my GUI”.

This really isn’t a zsh problem, but a “people putting too much stuff in a ‘getting started’ config”.

I used zsh for 15 years before looking at any plug-in manager, you can get a lot of the good stuff like the completion by just going through the first-run wizard included in zsh. A lot of stuff is included directly with zsh, including various prompt themes (which is what that tutorial wants extra fonts for, because they use a fancy prompt with custom glyphs; I don’t think any of the built-in ones need that)

Things like fuzzy history search with fzf is usually included with fzf’s distro package and the additional zsh-completions package for less used or newer commands is also packaged by most distros. In my experience, a lot of the other plugins are stuff that could be a standalone script instead of a plug-in anyway.