> While a simple series of steps it's still pretty complex compares to the equivalent in gdb:
Oh come on. If you're developing with visual studio, you've already got it open and have been compiling with it.
Debugging in VS is literally click the mouse where you want to stop, F5, full call stack/local variables there in front of you.
Given the list above, if you reproduce a similar list for gdb it is also pretty tedious: run a terminal emulator, spawn a new shell, cd to the directory you want to work in, compile the program with gcc with the appropriate flags, run gdb with the appropriate arguments.
I try to get into LibreOffice, but I just can't: on windows the ui is quite laggy, and the fonts just look... strange. It's like both the kerning and AA are off.
I've found every email client, mutt included, to be exceedingly difficult when trying to view your replies in the context of email thread. Gmail is the only one that does this seamlessly. If you get a ton of email, but never reply, or fire off so many replies that you never look back on them, maybe mutt works for you. For me the value of email and email clients is viewing the conversation as a thread, which importantly, must include my replies. You can find a few blog posts about configuring Mutt this way, it's complicated, convoluted, and always has side effects, like bcc'ing yourself. Outlook isn't all that much better in this regard as well, it does show your replies, but seems to loose them, or omit many from the thread.
Oh come on. If you're developing with visual studio, you've already got it open and have been compiling with it.
Debugging in VS is literally click the mouse where you want to stop, F5, full call stack/local variables there in front of you.
Given the list above, if you reproduce a similar list for gdb it is also pretty tedious: run a terminal emulator, spawn a new shell, cd to the directory you want to work in, compile the program with gcc with the appropriate flags, run gdb with the appropriate arguments.