I actually kinda agree with this.
Even if a commandline tool has more power, utility and flexibility than a gui tool, guis let you drill down into the core workflow of what your software is meant to do. At a minimum, it lets you segment what your regular users are expected to do from what your power users could use your software to do.
Additionally, if you intend for your software to be used by non-software adjacent users, a commandline interface is just asking for people to get lost/confused.
At work, we use ROS on some of our systems and while the commandline tools are simple to someone who works in the ecosystem, knowing what to look at when things go wrong is tricky.
Even a simple gui in tkinter that shows statuses or shows a list of topics and lets you print them out is leagues above the commandline when it comes to how much I need to be involved in other peoples' problems.
It is a luxury to be knowledgeable in software concepts and I think software devs/power users forget that often.
My piHole is the one thing that lets me use my phone without getting bombarded with ads. Best choice of my life. Set up Wireguard to VPN when out and about too.
I feel like the original guides are good but maybe compiling braindead simple guides would help mass adoption.