If your AMD card is older than your latest linux distro release it’s plug and play, no driver installation required
Wayland works pretty well on most desktop environments too

beware fresh released AMD cards in combination with long term release distros like Debian stable, you most likely will need the driver from the AMD website (not recommended)

the OLED version has a more efficient CPU and fan resulting in a quieter fan noise
if you only play with headphones or only play lesser graphical games like Slay the Spire or Brotato you probably barely would notice the difference though

It would be amazing if the runtime (per run) would be lowered
playing through three acts in one sitting is quite long, a runtime like Monster Train (40~90 minutes on non-speedrun time) would be pretty good

Arch Linux (like some other distros) also has a security tracker: https://security.archlinux.org/

In case someone doesn’t know it yet:

If you update your Arch Linux system with a kernel upgrade, the kernel modules will NOT be loaded again automatically by default and things like FUSE (used in AppImages for example or other FUSE based mounts) will not work without intervention

simple rebooting is the foolproof way or setting up kernel module reload hooks: https://archlinux.org/packages/extra/any/kernel-modules-hook/

there is no shame in asking question especially if you already put in some effort yourself and mention what you already tried

Just a little heads up in case you didn’t knew:
if you install packages like latte-dock from pacman (or build from source in this case) they will vanish with your next Steam Deck update because the Linux on the Steam Deck works quite different to a regular Linux installation

I wouldn’t get so much hung up on latte-dock anyway since it is unmaintained since quite some time and doesn’t even work on the latest KDE Plasma 6 (which SteamOS doesn’t have yet but will come in the near future)
customizing the default Plasma Panel (right click on desktop > enter edit mode > add panel) is your best bet nowadays for a similar look

anyway if you are really dead set on latte dock you will need to “initialize” all public keys first from the Arch Linux and Steam developers until you actually can install anything on the package manager pacman

pacman-key --init
pacman-key --populate archlinux
pacman-key --populate holo

the last line is specific for SteamOS only

the init command probably only works in Debian nowadays givin it’s a thing from the sysvinit era

Latte Dock users will need to say goodbye then

they waited until the first minor version which fixed already some bugs as expected
pretty nice release

you probably have old hardware in that case
the latest kernel releases greatly helped with the effiency of newer AMD and Intel (Hybrid) CPUs which can give you a longer battery usage on laptops

My Arch Linux Homeserver and VPS which ran since years are like: “huh?”

Not a single Ubuntu upgrade failure on my book anymore 🤞

this task is easy on gentoo but hard anywhere else
in the past I checked package updates via nvchecker, grabed the latest PKGBUILD via ABS, applied the patch, compiled the package and sent it to my custom repository
if you add the repository higher in your pacman.conf it will grab it from that first

but this a huge pita, even going through the route of maintaining an AUR package is simpler

hope this helps with the dumbster fire of the virtualbox version in the official Ubuntu repositories
(virtual box basically “breaks” on Ubuntu LTS once a newer HWE kernel gets released unless you install a newer version of it, leading to hundreds of support threads every time this happens)

.zip is already a thing
https://www.malwarebytes.com/blog/news/2023/05/zip-domains

boot time difference feels like in the realm of margin of error
the biggest difference however is that booster builds the initramfs much much faster while mkinitcpio slows down every kernel upgrade espcially on slower laptop cpus

I’m using Caddy (sometimes in a container or most of the time as system package) as reverse proxy mostly for containers
I try to minimize non-container services but they work well with Caddy too

Traefik is a tad more complex (still nowhere near Apache2 levels though) but scales more easily espcially if you only run containers and start/stop them programatically

if you are open to learn something new: Caddy webserver has a dead simple config, fetches tls certs by default for you and works with crowdsec too

If we are talking Silverblue then podman is your pick for everything Flatpack “can’t”
there is no big push for cli flatpack since this already a solved cause with containers for podman/docker/kubernetes

however no matter how you approach this you will always have dependency security issues
unless you built every flatpack/container yourself you are at the whim of the creator of it to keep every dependecy updated
this is already a known vulnerability factor in the container sphere on topbl of the threat of 0-day exploits

chances are you already used the external nvidia kernel module prior
the dkms package is just the “catch all” way which works on most setups
(at least on Arch Linux)