Our great sponsors
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
I use Debian stable and these are all the up to-date programs I need outside of the official Debian repository: Firefox https://www.mozilla.org/en-US/firefox/new/ Tor-Browser https://www.torproject.org/download/ Signal https://signal.org/en/download/ Kdenlive https://kdenlive.org/en/download/ And here are some things I get from Debian Backports: Newer Kernel yt-dlp In my use case what would switching to Debian testing accomplish? Nothing would change, so I figured I might as well stay on stable. That's the same question you have to ask yourself: "What am I actually accomplishing by using testing instead of stable?" Do you care if some python packages are up to date? Is it the end of your world if gimp is one version behind? Probably not. I don't use snaps or flatpaks because I don't want to take care of multiple package managers. In my opinion this defeats the purpose for the reason you switched to Debian. Debian is a boring distribution. It is supposed to just run on your server or your workstation. Or have fun and do what you want with your distro. Either way is fine. :)
This is the exact version, which is available on Flathub so Flatpak can be avoided (in this case), which is a huge thing!
A few days ago I used the official deb package from signal.org and the software is running much smoother now. With Flatpak it permanently used ~14% of my CPU (even in the background). Now it only uses <4%. Flatpak is just not sustainable...