bauh VS oxipng

Like bauh which supports AppImage, Arch packages (including AUR), Debian packages, Flatpak, Snap and native Web applications

github/vinifmor/bauh

If you really want a GUI package manager that doesn't break EndeavourOS, I've had a good experience with bauh when I started using EOS. But I also do everything with yay now, as others have suggested, it is more convenient once you know the commands.

Lastly, deb-get + pacstall + bauh. All of these combined covers 99% of my software needs, much less need to find and install PPAs and .deb manually. Still not as convenient as AUR, but much better than it was before. Hopefully, eventually everything is on Flatpak, snap, or AppImage so I could just use Bauh for most apps, but for now, I'm glad that these tools exists.

Is it an AppImage? Did you make it executable? If you use a lot of AppImages then you may want to add DE integration via their utility. I do not use it, as it runs a backgroudn daemon, I prefer using bauh instead.

Bauh https://github.com/vinifmor/bauh

You can use bauh. Supports AppImage, Arch packages (including AUR), Debian packages, Flatpak, Snap and native Web applications. GitHub

You may wanna take a look at bauh.

Although, if I had to I would personally suggest bauh if you want a graphical package manager. I haven't had any issues with using it, and neither have I seen people complaining about it. It also supports the following formats: AUR packages, AppImages, Flatpak, Snap and Web applications. It also integrates with Timeshift to provide a simple and safe backup process before applying changes to your system.

I have had good experiences with https://github.com/shssoichiro/oxipng . Although, I suspect this wouldn't give you nearly enough space savings as jpg.

If you do want the file as a PNG (for transparency and a common format that's well supported), but don't want it so huge, consider something like oxipng. https://github.com/shssoichiro/oxipng

oxipng, pngquant and svgcleaner — optimizing images

I wonder how `pngcrush` compares to `oxipng` (https://github.com/shssoichiro/oxipng).

Personally, I use `oxipng` if I want lossless compression. However, most of the time, I use `pngquant` instead, since it gives significant size reduction even at `99%` (I can't even distinguish between the original and reduced image).

    pngquant --quality=99 --ext=.png --force file.png

Depending on your workflow it might make sense to export PNGs directly from Affinity and then reduce their size with a utility like Oxipng, which uses all your cores to find the best algorithm for each particular image.

Assuming your frames are PNG files, you could use a lossless optimizer like optipng to try if their size can be reduced. I prefer oxipng, which is faster and multithreaded, and seems to have more active development.

Not sure what extensions of images you use, but if they’re PNG you could use oxipng: https://github.com/shssoichiro/oxipng