Proton-Caller VS dust

Since I couldn't get get with Proton 8 to work with Proton-Caller, I went with this standalone script:

Yeah pretty much. Check out Proton Caller: https://github.com/caverym/proton-caller

It's funny, I spent the time to get a windows app launching in proton as I was having some issues with the Linux version that I didn't have the time/patience to diagnose and fix myself.

The launcher is called proton-call ... I changed Steam to use the version of proton to match what the app expected, and it worked pretty cleanly. All said, I do wish it were easier for a separate launcher or third party to include proton as a separate package.

https://github.com/caverym/proton-caller

This tool can be installed through package manager in any Debian and Arch based distros. Also, it can be manually built and complied from source code. (here's the github link if you want to check it now: https://github.com/caverym/Proton-Caller/)

Run it through proton-caller instead of steam itself

As someone who owns a crap ton of games, Proton-GE works for every single game that are supposed to be working on Linux for me. I use it in conjunction with proton-caller, they just work. Not sure where this things are likely to break in subtle ways comes from.

Proton is not inseparably tied to Steam; you can easily run it outside that environment, and projects like proton-caller make it dead simple.

proton-caller https://github.com/caverym/proton-caller

i use proton-caller and find it easier to manage non-steam games that way. heroic game launcher and bottles should be easier though.

Yes it is. But it's not recommended.

Try using dust https://github.com/bootandy/dust

Folks open to using gdu might like to try dust (6k stars), or even erdtree (1.4k stars) which is too recent to show up on lists like this and still a bit behind on stars. A lot of people seem to use starship (33k stars) though I'm personally oldschool on prompts. There are many other items on that list I'm not motivated to check.

The first thought I had was to use rayon for this. And looking at some prior art that does pretty much the exact same thing, it does indeed use rayon.

The dust CLI command (made with Rust) can do this too.

How does this compare to dust?

Happened to me this morning, something filled up my drive in minutes. I used dust[1] to look for large files while it was happening but knowing what was doing it would've been a big help.

[1] https://github.com/bootandy/dust

dust is also really nice.