What are the best practices for handling software installed from .zip files on Linux?

It's a good move to keep your software organized. I suggest placing it in `~/.local/share/` and then creating a symbolic link in `~/.local/bin`. This way, you can easily run the application from the command line or your desktop environment launcher, though it's not the same as a traditional desktop shortcut. It streamlines access while keeping your system tidy!

For software installation, the Filesystem Hierarchy Standard suggests using `/usr/local` for non-distro software. Sometimes, `/opt` is suitable for larger third-party applications. I keep smaller utilities in my `~/.local/bin`, but others prefer `~/.bin` for a more streamlined home directory. To create desktop shortcuts, just look up how to make `.desktop` files. It's straightforward! As for software offered as just a .zip, developers often focus on making the application itself without juggling multiple package formats, especially since Linux usage is a small portion of their overall user base. Providing updates and managing dependencies for various distros can be a daunting task, which may contribute to their choice.

To create a desktop shortcut, you’ll want to use `.desktop` files. These live in `~/.local/share/applications` for user-installed software or `/usr/share/applications` for system-wide apps. You can check existing `.desktop` files in these locations to see the format. Just open one with a text editor for a clear example!

I got a bit curious about your YouTube client, so I did a quick search and found that it's available in the Arch User Repository (AUR) and on Flathub. If you install Flatpak, you can manage your applications easily and get updates without the hassle of manual management. The AUR is another common method for software management—both approaches take care of shortcuts, downloading, and installations for you.

It's good to be cautious with software that's only available for download directly. This can potentially be a way to distribute malware, but it's less common on Linux. Remember, there's no standard installation or uninstallation process with these setups. If I need to use something like that, I typically place it in `$HOME/bin` for user-only access or `/usr/local/bin` for system-wide availability. You can also create a GUI shortcut by making a `.desktop` file, which all major desktop environments recognize. There's plenty of documentation about the process online if you want to dig into that!