Question is how “real” that support is - firmware updates matter and depend mostly on the chip manufacturer’s support.

By 8 years old even the newest devices will be out of software support and using EOL phones is not a particularly great idea for security. GOS’s security focus goes out the window if you use an old version with known vulnerabilities.

You can probably expect GOS support as long as Google supports the device, that is the main limitation. For the newer Pixels that is promised to be 7 years after release.

Going by this table, Pixel 6 is currently the oldest to get full GOS updates

That matches Google’s software support

Don’t buy ASUS, they have a terrible security record. At this point I would trust only MikroTik and Ubiquiti.

Due to the way Flatpak deals with nvidia drivers, you need to run flatpak update after any time the nvidia drivers update and you reboot the system. Thankfully you do not need to reboot after updating only flatpaks. Could not find a good source for this now, unfortunately.

As for the “why?” - flatpak apps do not contain the userspace parts of the nvidia driver required to use the GPU properly, they come packaged as separate runtimes. These nvidia driver runtimes need to match the specific driver version you are currently running. If they don’t match, flatpak downloads the right runtimes when updating.

Even worse - it looks like Google might be forced to sell Chrome to some AI company.

What does it matter? They all rely on Mozilla to do the hard work - maintenance and keeping up with web standards, and then just slap a couple of features and customizations on top of it. If Mozilla dies the current forks are dead in the water.

A lot? All of them.

All the kernel Rust code is GPL, so you can leave that slippery slope alone. MIT licenced core utils just leave the door open to eventually using them in the BSDs as well.

Then the answer is definitely not - at the very least Wine would need to simulate a very large part of the NT kernel.

I’m not sure what a flatpak version could possibly do any better than the version I use.

The official OBS flatpak supports more codecs and integrations than some distro packages.

Stability is also a factor, especially on rolling or cutting edge distros. Fedora RPM release of Blender did not work for me at all with an nvidia GPU, for example.

If you have multiple monitors with different refresh rates, you’ll notice immediately.

AFAIK no systemd -> no flatpak -> don’t recommend to newbs. Say what you will about flatpak, but it is the official distribution method for some popular pieces of software and large GUI software generally works better through it (in my experience) - think Blender, GIMP etc.

nvtop also works with AMD now and is way nicer than radeontop IMO

What’s wrong with Jerboa? Been using it since I left reddit, seems perfectly fine to me.

If you’re thinking about the recent thing, the real Go library (boltdb/bolt) was not compromised at all. The malware was in a similarly named package (boltdb-go/bolt), this is called “typosquatting”.

Link to article

IME it substantially increased download speeds as well. There’s stuff that I would not have gotten at all without port forwarding.

AFAIK that’s exactly what it does.

Interesting, I’ve had 3 Gigabyte MOBOs and GPUs. One GPU died after 6 years, which is unfortunate, but seems reasonable. First MOBO is still going strong 10 years later. Have had no issues otherwise.

Well, for example, my MOBOs Ethernet requires the Realtek out of tree drivers (at least it still did on 6.11), which don’t always compile on the current kernel. Ironically, the WiFi works fine.