• 0 Posts
  • 44 Comments
Joined 2 months ago
cake
Cake day: August 7th, 2025

help-circle


  • They lucked into it. They made their cards for gamers, and various groups, AI researchers, bitcoin miners and others, discovered that they those gamer GPUs were really good for other tasks too. I think it took a while before Nvidia started making specialised cards for those purposes.

    I can’t really blame them for serving that market that they just lucked into. I can and will blame them for their terrible Linux support.










  • This does sound very interesting. I should have said the debuggers I’m familiar with don’t do it. Or if they do, I have no idea how.

    Certainly setting breakpoints on certain conditions instead of just a line, would help a lot. Being able to step backwards through the execution even more so.


  • I can also see the variables change by logging them.

    Debuggers are great if you want to see in detail what’s going on in a specific loop or something, but across a big application with a framework that handles lots of things in unreadable code, multiple components modifying your state, async code, etc.; debuggers are a terrible way to track what’s going on.

    And often when I’ve found where it goes wrong, I want to check what was happening in a previous bit of code, a previous iteration or call. Debuggers don’t go back; you have to restart and run through the whole thing, again finding exactly where it went wrong, but now just a bit before that, which is often impossible.

    With logging, you just log everything, print a big warning where the thing has gone wrong, and scroll back a bit.

    Debuggers are a fantastic bit of technology, but in practice, simple logging has helped me far more often. That said, there are issues where debuggers do beat logging, but they’re a small minority in my experience. Still useful to know both tools.