Kann aus eigener Erfahrung berichten, dass dabei der Durchsatz leider oft auch nicht berauschend ist.

But then why bother to package the game for the distro in the first place?

Deswegen habe ich die Hoffnung, dass sich Typst mittelfristig zu einer echten Alternative entwickelt. TeX merkt man seiner Alter leider an. Vieles würde man heute anders machen. Da Typst ein komplett neu entwickeltes Textsatzsystem ist, können sie alte Zöpfe abschneiden und müssen nicht den Ballast eines halben Jahrhunderts mitschleppen. Es ist beeindruckend, was das Projekt schon erreicht hat.

There‘s no reason not to use both. For some things a GUI file manager is more convenient.

32 GB should be plenty of RAM for this scenario.

deleted by creator

tl;dr Duplicity does full or incremental backups, BorgBackup only does full backups but with deduplication.

After the first backup with Duplicity, you can choose to do an incremental backup which will only store the data that has changed since the last backup. This saves time and disk space but you have to do slow full backups regularly. See question 3 of the FAQ.

BorgBackup alway does a full backup. But it divides all data into chunks or blocks (don’t know what they call it exactly at the moment). It then hashes those chunks and stores them in a content-addressed storage layer. So it basically works like Git under the hood (plus encryption). If a chunk doesn’t change between backups it‘s already there and does not have to be stored again. A backup is always a full index of the data.

With today‘s fast processors and hashing algorithms, a backup with Borg should be just as fast as an incremental backup with Duplicity. If you ask me deduplicated backups are just plain superior.

Another tool that works like BorgBackup is Restic, which I prefer. Both are good choices that I would trust with my data.

Do you know what takes up the space? Something like gdu or ncdu will help you analyze the problem.