Debian is on a roughly 2 year release cycle, and typically has a 6 month (-ish) freeze leading up to the release. So software in the stable release will generally be somewhere between 6 months and 2 years out of date. (My math might be a bit off but hopefully you get the idea).

Ultimately, it comes down to how you use your system, and what you need/want from your software. What you consider to be “the things that matter” will really be the deciding factor here. Need the occasional newer version of an application or library? It’s probably fine. Need the latest, greatest desktop environment? You may want to pass.

There are a number of ways to install newer versions. Backports, if it has what you want, is the easiest and safest.

There are other ways as well, but depending on what method you choose and what software it is, you may need to be careful not to break something. (I’d recommend not adding random third-party deb repositories for this reason).

Flatpak seems reasonable, but I haven’t used it much (once or twice I think). I typically use backports, or occasionally do my own local backports from sid.

Snap and AppImage are also possibilities. I don’t use snap, and I think I installed something proprietary by AppImage exactly once.

If it’s not in Debian at all, then I need to handle that a bit differently. But to me that’s a different issue than the ‘old version’ issue that Debian is often derided for.

Anecdotally, I’ve been daily-driving Debian stable (including for gaming) for over 20 years, and it suits my needs well. But of course, YMMV.

Interesting bee fact -

In a hive that has been queenless for a period of time (long enough that there’s no way they can raise a replacement queen), one or more workers may develop the ability to lay unfertilized eggs.

Due to how honeybee genetics work, those unfertilized eggs can hatch into drones (males), which may then have the opportunity to mate with queens from nearby colonies.

I guess this is sort of a last ditch effort to propagate the hive’s genetic material before it fizzles out and dies. Which I think is fascinating.

I haven’t tried this so I can’t vouch for it, but it looks like you can add custom domains to a whitelist per https://support.mozilla.org/en-US/questions/1292986

So in your case, something like

browser.fixup.domainsuffixwhitelist.work = true

may work.

I don’t have an alternative program to suggest, but there are some workarounds for using redshift.

First, in the config file, you can set the location provider to manual, then specify a lat/lon and it will use that location in its time calculations. I do this on my laptop, and it works well except for when I cross multiple timezones - things are obviously off a bit.

Second, with the caveat that I haven’t tried this, it looks like you can also manually set dawn/dusk times in the config, which sounds like what you’re after.

See man 1 redshift for more info.