this post was submitted on 05 Jan 2025
589 points (95.8% liked)
196
17586 readers
345 users here now
Be sure to follow the rule before you head out.
Rule: You must post before you leave.
Other rules
Behavior rules:
- No bigotry (transphobia, racism, etc…)
- No genocide denial
- No support for authoritarian behaviour (incl. Tankies)
- No namecalling
- Accounts from lemmygrad.ml, threads.net, or hexbear.net are held to higher standards
- Other things seen as cleary bad
Posting rules:
- No AI generated content (DALL-E etc…)
- No advertisements
- No gore / violence
- Mutual aid posts are not allowed
NSFW: NSFW content is permitted but it must be tagged and have content warnings. Anything that doesn't adhere to this will be removed. Content warnings should be added like: [penis], [explicit description of sex]. Non-sexualized breasts of any gender are not considered inappropriate and therefore do not need to be blurred/tagged.
If you have any questions, feel free to contact us on our matrix channel or email.
Other 196's:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Debuggers run in command line, making them less accessable to the average person, so they need to learn the commands to get it running.
Same is true for Windows.
Frankly you cannot get around the command line when developing.
Most Windows debuggers have a GUI, including Microsoft's own offerings, and even 3rd party ones (I use RemedyBG) have one.
Fair, but for those there presumably is a CLI as well? And conversely, what is stopping you from using a GUI debugger onLinux?
I was more thinking along the lines: you'd be hardpressed to find a debugger that does not have a CLI