I have barely any experience with raw gdb, but debugging is something that allows for a lot of contextual actions. Even just placing a breakpoint is simpler if you can click the line instead of copy-pasting the line number. But also evaluating expresssions while on a breakpoint, or a graph with an overview of all threads. I doubt these are straight-forward commands in gdb, and if they are, you need to figure out the exact parameters (like line number).

Furthermore, I have tried raw gdb once, and got super confused as to what I was supposed to do or look at. Yet every IDE makes it trivial to use debuggers. Learning the options available to you is much easier in a well designed GUI.

Thank you!
Sorry for the cloud error, the server's origin website is hosted in my country Iran, which is currently in a semi-blackout and very bad internet distruptions. Very sad.

You might see the blog if you try a couple times more, I can see it with most VPNs.

I completely agree with your points. I'm stating the same sentiment in the blog.

I prefer GUIs for two things:

1. Things that are inherently graphical (gimp, blender, etc)
2. Things that I don't use very often, and the GUI is too simple to be bothered with a cli.

I do actually and I also prefer CLI, just wanted add a bit of nuance to the discussion.