He clearly hasn't met elfeed that you run from within Emacs; I've used all of the major RSS readers over the years and elfeed is unbelievably versatile as are most things in Emacs, but learning Emacs might be worth it just for elfeed and org-mode.
This is going to be an off the wall statement given this audience, but WWE signed an exclusive deal with NetFlix for 10 years I think in an effort to counter their main competitor AEW, which signed a deal with HBO Max shortly before that. Now they'll both potentially be on the same platform, which WWE will hate as it will be interesting in having two competitive pro wrestling promotions on the same platform.
What is love? Baby don't reboot me, baby don't reboot me :) Truly a rock solid OS and I use it for my personal DNS servers and never had any issue, it just run and runs and runs with minimal bloat. I think it's way more stable than Linux, but obviously has some work to be a comptetive desktop. I've recently developed the philosophy of using Omarchy as my desktop and servers are FreeBSD unless there's some reason it doesn't fit my use case.
I use Slack as my bookmark manager ;) Have my own personal Slack workspace where I have various channels for certain types of bookmarks(coding/emacs/history,etc). On my Debian box at home I have weechat with the weeslack plugin where my weechat instance runs in a tmux session 24X7 and I log everything locally to disk. That way I can just open up the Slack log for a given channel to find a specific bookmark in Emacs via search/regex search. Have Slack clients at work, mobile, and home, so it seems to work pretty good for me.
This also demonstrates were CLI excels and where GUI's fall short. With the GUI your just stuck digging for the correct option and tab. With the CLI you can create aliases or shell scripts to make wrappers for complex CLI options. Not to mention building custom openssl.cnf configs.
The other thing is that not all sysadmins are security engineers and you essentially have to be one to be able to manage SELinux well. You really have to understand the security implications of incorporating policy X for application Y.
Minimally, Redhat needs to come up with some better documentation around managing it along with better tools for managing policy. Like say, exporting the existing policy set before each upgrade or policy change and import them back? I'm thinking sort of what is done when a package is updated and you are prompted if you want to keep or replace your existing configs.