Heroic user here. You can use this feature to apply .exe patches:

In my case, I didn't see any advantages compared to public trackers. Users of private trackers are supposedly all so elite, but in reality they pay for seedboxes and try to be the first to download literally every new release to at least somehow support the ratio around 1.0.

Guys, while you seed all sorts of junk for the sake of who knows what, I seed really useful content on public trackers and have a ratio of 99.3, which in fact does not affect anything.

There are normal private trackers, of course, such as Milkie, but there are a lot of dead torrents there.

I've never understood why GNU/Linux actually needs swap. Okay, I created a 4G partition for it, having 32G of RAM. I never used all that RAM, but even so, stuff regularly ends up in swap. Why does the OS waste write cycles on my SSD if it doesn't have to?

However, if I artificially fill up all 32G of RAM, the system almost completely freezes faster than switching to using swap as a "lifeline". And it only comes back to life when OOM Killer finally remembers its existence and kills some f__ing important process.

Have you tried Debian?

You can use tools like spotdl and yt-dlp to download songs from YouTube music and Spotify

To get quality like this https://youtu.be/cX4KA-AFS9M ? Nah thanks.

In Elixir, we mark statuses by using a question mark at the end of the variable name. Something like this:

authorized? = user |> get_something() |> ensure_authorized?()

I like this better than the is_ prefix

console.log() is really easy to learn, but what happens after that is a complete "wtf"

The language idea is good, but: THREE.WebGLRenderer: A WebGL context could not be created. Reason: WebGL is currently disabled.

Seriously? Why do I need WebGL to read TEXT in docs? :/

Don't forget https://zed.dev/docs/telemetry

This way we will have multiple sudo-tools on one system without the ability to remove all but one. Like now with all this crap like systemd-resolved, systemd-networkd, systemd-anothershitd and a bunch of tools that do the same thing, but are all required.

Try not to work in pitch darkness :)

Just build the app on very old distros like Ubuntu 16.04 if possible. But in general, packaging should be handled by the maintainer. If you want to be both a developer and maintainer, packaging problems will take up 75% of your time.

It's not really hard for us users to follow your README and just copy the built binary to ~/.local/bin.