X3I

Well yes but I am not sure that this is the main problem with flatpak containers.

I’d rather point out that this approach creates a bigger attack surface since the containers tend to ship with outdated versions of libraries, frameworks and tools that the actual application relies on because it is now that specific app developer’s problem to update them inside of the container. So with this, even an up to date system is not really up to date and might suffer from severe vulnerabilities. I’d say it depends on your application, use case and threat scenario; containerization can make sense but is not the holy grail.

Did you take a little journey into the BIOS yet? Is definitely firmware, the question is if you can just change a setting there. Otherwise, somebody already mentioned dummy HDMI plugs.

Relied on an AUR package for building and signing my unified kernel image… one day it was outdated and geberating the image failed, I noticed that by the fact that the system refused to boot my OS. Fixing it was done in a few minutes but boy, that was a shock :D

Guess who also checks the exact output of the kernel rebuild now before rebooting!

This will help: https://wiki.archlinux.org/title/Dual_boot_with_Windows

Applies to PopOS the same way, except for installation steps involving pacman. I’d revommend going with systemd-boot instead of grub, not sure what Pop ships.

Vim supports editing files through scp as well, no reason to cry here xD

Very true also for the opposite direction; I am daily driving an HP Elite Dragonfly for work and my Elite x360 1030 G2 for private and both work almost flawlessly despite no official Linux support. I have to disclaim that I never tested the Fingerprint reader or IR face recognition crap. But microphone, orientation sensors, webcam, keyboard, trackpad all work extremely well (Arch linux).

It always comes down to the individual hardware it seems.