I should’ve done my homework before replying then :)

Just vote for some other millionaire to represent you, easy as that.

Just so that you have an additional data point, here’s how I do it.

I run a backup first, using borg-backup. I used rsync in the past, then rsnapshot and now borg since it allows for compressed incremental backups, diffing on the “chunk” level, meaning I won’t backup the entirety of a modified file again and safe a lot of space.

I used yay before, but like you I didn’t want to go into it blindly and do some modicum of sanity-checking the PKGBUILD for changes beforehand. Since it wasn’t obvious on what would be the best way of using yay for doing this, I asked around on the ArchLinux Forum, and ultimately decided to try one of the simpler tools suggested in the Arch Wiki, aurutils.

After setting it up (the author helped me migrate), I now use it as follows:

• aur repo --upgrades: Searches for new versions of aur packages and displays them
• aur sync --upgrades --no-build: Performs a git-pull under ~/.cache/aurutils/sync and opens vifm so that I can look at a diff of the PKGBUILD and all the other changes in the affected directory.
• aur sync --upgrades --no-view: Builds the package. It is now available as part of the custom (local) repository used only for aur packages, but hasn’t been upgraded yet. That is, a package.tar.gz or whatever has been created and put into ~/.cache/aurutils/sync/, where the PKGBUILD resides as well
• sudo pacman -Syu: Upgrades all packages from all repositories, including the ones from the custom repository

I won’t argue pro or against one aur helper or the other, but I feel like I have a little more insight about what happens under the hood since I made the switch. That being said, in the very beginning, I managed aur packages manually. This works also, but at some point became too tedious for my taste. I am happy with the semi-automatic approach I am using now.

Ich benutze seit Jahren borgbackup, nachdem ich zuerst mit rsync und dann rsnapshot angefangen hatte. Automatisches Backup erfolgt denke ich entweder über udev-Regeln (Backup beim Anschließen), oder in regelmäßigen Intervallen (benutze ich nicht) wie z.B. hier beschrieben.

Borg hat im Gegensatz zu rsync rsnapshot den Vorteil, dass auf der Sub-File-Ebene dedupliziert wird, d.h. nur weil eine Datei sich an einer Stelle geändert hat, wird der Rest der Datei nicht nocheinmal kopiert. Das einzige was ich zusätzlich empfehlen würde, wäre von vornherein mit compression --zstd,9 oder so zu arbeiten.

Although the relevant links have already been provided, the gist is

• Acme stands for some “generic” editor here, where you have to use the mouse a lot, which is perceived as slow
• Emacs is known to be very powerful (to the extend of being called an “OS with a bad editor”), but using unergonomic keyboard shortcuts
• Vim is an editor that has been designed for keyboard power users in mind, but which has the reputation of being difficult to learn

I find this unnecessarily derisive. There are good reasons for a UI or README not being user-friendly, the top-most one being (imo) that it is really, really hard to get right, takes a lot of time and doesn’t primarily solve the problem the project was started for.

Mir hat ein Dozent sich aus dem Grund mal verweigert, das Kurspasswort für die Vorlesungsmaterialien mitzuteilen. Ich war an dem Termin als das mitgeteilt wurde nicht in der Vorlesung weil ich eben arbeiten musste, was von dem Dozenten mit dem Kommentar “ja das ist dann eben sehr schlecht” versehen wurde.

Es kommt aber auch sicher auf Studiengang und Hochschulort an wie (un-)gern das gesehen ist.

Laut einem Nutzerkommentar auf Heise (also aus erster Quelle!) ist dieses Outlook nur eine gewrappte Webapp und lädt, wenn man offline ist, nicht mal die UI.

In Bayern setzt man lieber auf mobile Windräder, a.k.a. Flugtaxis.

and then suddenly there’s the perfect use case

Yeah but like WHAT?