This isn't foolproof. A lot of malware these days is resistant to analysis because they can detect that they're running in a sandbox and refuse to run the malicioua code.
Yeah, if you've got two EFI partitions on separate disks and one is for Windows while the other is for your Linux, you're good. Windows likes to reinstall its bootloader which sets it as the default and sometimes overwrites the Linux bootloader, but not if it's on a different EFI partition, then it doesn't "know" about it.
This is with systemd-boot, which I switched to because it's easier to use a unified kernel image with, but it should work just fine with grub as well. The last step will sign everything that needs to be signed, including grub and the kernel images.
You only need to trigger a re-sign if you update grub using grub-install. If you just change the grub config, you don't need to re-sign it because the config is loaded once the signed grub is already booted. This is another reason why I went with systemd-boot and unified kernel images, because I work with sensitive data and maybe I'm a bit too paranoid, and don't want anyone to be able to tamper with my boot in any way. This is also possible with grub and using an encrypted boot partition, but systemd + UKI + full system encryption was just easier. If you're not worried about evil maid attacks and just want secure boot, grub will work with no additional setup.
No issues with the pacman hook, it triggers every time there's a kernel update or nvidia update, and since I'm using mkinitcpio and UKI, the signing is usually already done by mkinitcpio before the pacman hook is ran, so the pacman hook doesn't really ever do anything. It's all done in the mkinitcpio hook.
As for bricking your motherboard, this only happens if your motherboard or any other component uses the microsoft vendor keys as part of the boot sequence, and it's only really a hard brick if it's your motherboard that uses it. If it's any other component, you can remove it and readd the microsoft keys and it'll work again when you add the component back.
And the key part here is replacing the platform keys. If you just always use the -m flag on sbctl enroll-keys, you'll enroll both your own keys and microsoft's, meaning no replacing necessary. If you always use -m, there's no real risk really, because you'll always add the microsoft keys that your hardware might need. Plus, if you're dual booting with windows, you need the -m to have windows secure boot work, anyway.
If you're extra paranoid, you can also add the -f option which should also include all the keys that your motherboard comes with by default, if it contains more than just microsoft's keys, but this shouldn't really be necessary.
I'm saying this as someone who has a self-signed key + kernel + bootloader + dual boot with windows. I have Arch and I dual boot windows, and the setup was literally three commands.
Enable secure boot setup mode and then do the following:
sbctl create-keys to create the keys
sbctl enroll-keys -m to enroll the keys to BIOS, including microsoft keys
sbctl verify | sed -E 's|^.* (/.+) is not signed$|sbctl sign -s "\1"|e' to sign everything that needs to be signed.
And everything is signed automatically on an update with a pacman hook that comes by default when installing sbctl.
That wiki entry lists all the possible ways to do it, for all combinations of bootloaders and secure boot tools. You only need one of them, for example 3.1.4. which is what I just described.
game-performance is CachyOS' script to set the power profile to performance while the game is running and restore it to what it was before when the game closes.
game-performance is CachyOS' script to set the power profile to performance while the game is running and restore it to what it was before when the game closes.
Because Linux is a monolithic kernel. What that means, essentially, is that it contains all the drivers and everything else, unlike windows which uses a microkernel. The advantages of a monolithic kernel are, for instance, that you don't need to install drivers manually, and you don't have to depend on potentially malicious websites to host those drivers. Additionally, if any kernel ABI changes for one reason or the other, say there is a refactor to fix a vulnerability, whoever does the refactor would also refactor the driver code because that is in the kernel, and the kernel won't compile if there's an error in the drivers. This way, the driver is always updated, and you don't have a situation where you have really old drivers that no longer work.
The disadvantage of a monolithic kernel is that there's a lot more code that you have to take care of, and the kernel has a lot more responsibilities as opposed to a microkernel.
Those are called Progressive Web Apps (PWA). You can use firefox to add the website to your desktop like this: https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/Installing
Once you do, when you open the app it should have just the website without the tabs and everything else firefox does.