Compactor VS delta

You can already do the very basic version of that by using Compactor. Essentially it uses Windows 10's compression algorithms to make your games smaller. A lot of variance between games based on what their files consist of, but I generally get ~25% more space on my drives. Of course, a single update to the game might mean that you have to pack them again, but it's still a pretty good upside with practically no performance loss.

This will also help.

ARK practically needs its own 500GB SSD, specially if you start installing mods on top of having all of the DLCs. However, it's possible to bring down its size massively if you use this software, it works exceptionally well in ARK, being able to reduce it to about half its size. For example, my ARK installation went from like 320 GB to 175 I believe, which is still huge, but only about as much as any modern AAA game.

You can chuck compact.exe at it by hand (use the /exe option), or if you'd prefer to avoid the command line there's my Compactor tool, or the venerable CompactGUI.

They actually don't compress it. Using a simple compressor like this one for instance, the size decreases by half, if not a bit more than it. Tested it with the base game and it went from 200GB to 100GB.

I should press on and finish my Compactor rewrite, I guess.

7zip, microsoft powertoys (useful utilities n stuff), hyper-v (VM stuff), OBS, optimizer (https://github.com/hellzerg/optimizer) (privacy stuff + system tweaks), compactor (https://github.com/Freaky/Compactor) (uses windows compact.exe and provides a GUI for a otherwise cmd based tool) also qbittorrent

Thanks for the difftastic & zoxide tips.

However, I've been using this git pager/difftool: https://github.com/dandavison/delta

While it's not structural like difft, it does produce more readable output for me (at least when scrolling fast through git log -p /scanning quickly

View on GitHub

I'm currently waiting on the integration between Delta and Difftastic:

https://github.com/dandavison/delta/issues/535

Difftastic now has JSON output, whic should make it much easier to build this.

I'm surely in the minority here. I've been using Emacs for almost a decade now, but I just can't get into the Magit workflow. I've tried several times, but always end up going back to Git on the command line. I have dozens of aliases, shell integrations, a nice diff viewer[1], etc., and interacting with Git has become muscle memory. I can commit, cherry-pick, rebase, bisect, fix conflicts, etc., in a fraction of the time it would take me to navigate Magit's UI. I'm sure with enough practice, a Magit user could do this more quickly and efficiently, but honestly, with some custom-built porcelain, Git's UI is not so bad. Though this could very well be Stockholm syndrome after using it for such a long time...

For whatever reason, Magit's opinionated workflows never clicked with me. A part of it is the concern that it will do something weird to my repo that I'll then have to waste more time undoing manually. I usually don't trust sugary wrappers around tools. And another is the fact I don't use Emacs on all machines, and setting up Git on a remote system is just a matter of copying over my config and some shell integrations.

Also, on a more personal note, I find the cultish fanboyism whenever Magit is brought up slightly offputting. Does anyone have anything bad to say about it? No software can realistically be this infallible. :)

[1]: https://github.com/dandavison/delta

For looking at diffs I still prefer the command line though, and use delta to view diffs between commits or branches.