No thank you. I would rather engage in more productive activities like cutting my lawn with scissors.
Discussion
Absolutely, you do you - But not correct to say Desktop Linux is horrible now, when the fact is, Linux allows you to take out what you don't want. If you're willing to go through the effort of cutting your lawn with scissors, but not uninstall some garbage packages to keep the machine you use to connect to the world clean and in a known state to yourself (or just put it together in 10 mins as arch allows), then I think that's a different issue entirely.
Tell me how to get verified boot with desktop Linux.
Ubuntu has it, right?
Some distros have this built-in. Others, and for instance with arch, you can use sbctl which automates most of the process, by having you create keys, enrolling them, and then signing the boot files (this is with the default arch bootloader, systemd-boot).
This doesn't verify the firmware.
Irrelevant - BIOS and UEFI for the purposes of secureboot only care about the kernel files and the bootloader. And in the case of UEFI, you can bypass bootloader and directly launch the kernel.
Relevant to me.
SecureBoot is not verified boot. Verified boot is a lot more extensive. There is no way desktop Linux can do it. No matter how many commands you type.