It seems you have not read the post or you don't have experience with gdb or with Linux debuggers/ide combos. He's debugging zig, but his issues are with the ux and iirc he mentions few zig-specific bugs. I have been through the same ordeals while debugging C++ on Linux. In the end, there's only gdb with a command line interface. Couldn't get any nice IDE with watch, memory view or even simple breakpoints to work. Some have a few of those features but none has all of them working. Eg. if you have a working breakpoint it'll fail to properly inspect STL containers etc.
I'm sure there are many people saying "works on my machine", but it never worked on any of mine, sadly. Visual Studio simply works and has a nice, intuitive interface. Pressing F10 to step over will always be better than typing something in the gdb command line and hitting Enter.
I haven’t had any trouble doing graphical debugging with VSCode and the C/C++ plugin. I get breakpoints, locals, watch, etc. The one thing I miss from Visual Studio is being able to easily change the watch window display format (e.g. showing a number as hex).
I'm sure there are many people saying "works on my machine", but it never worked on any of mine, sadly. Visual Studio simply works and has a nice, intuitive interface. Pressing F10 to step over will always be better than typing something in the gdb command line and hitting Enter.