Unfortunately with iOS you are stuck with Obsidian Sync because Syncthing does not work because of the permission model. Otherwise I prefer Obsidian over Joplin for the above mentioned reasons and nice extension ecosystem. It's easy to get your files out of Obsidian, no vendor lock-in

Sounds like you have installed protobuf via Home Manager or nix-profile and/or are using the system's compiler instead of one installed through nix?

All compilers in the nix package store are wrapped in custom shell scripts that injects the needed paths the compilers are looking for in FHS directories. In case of gcc glibc and libcxx, as well as $NIX_COMPILER_FLAGS (name from the top if my head) which is populated by nix depending on what is installed. For example, if you would use a nix development shell (classic or flake based) and install protobuf there, the correct include paths the wrapped compiler needs would be contained in this variable.

Have a look at https://nixos.wiki/wiki/C which answers a few questions and look at the wrapper code of gcc (in the gcc package) which points to gcc-unwrapped.

What was your experience with the Charybdis Nano in general? Do you hands need to hover over the desk or does a wrist pad suffices?

I had good experience with BorgBackup and restic. However, I've settled with restic since it had the right back ends for me that Borg did not have and I rather like it's just one static binary instead of Python+C.

As far as I can see, BorgBackup has a bus factor of one while restic has two to three active contributers.

Other than that, they are quite comparable, I think.

I use flash.nvim extensively to jump around. There are also %, [[, [(, etc to work with brackets. vim-multicursor-visual helps to find and edit multi occurrences.

And for the rest I have a an easily reachable layer on my programmable keyboard with arrow keys in the home row instead of QWERTY ghjk

AFAIK installing packages via HM does not automatically give you the right includes. Either set $NIX_CFLAGS_COMPILE (and potentially $NIX_LDFLAGS) manually (or pass -I argument to the compiler or use a development shell while declaring your inputs (protobuf) there. This will then automatically populate the aforementioned env variables automagically.