Well indeed, I could have said, "this is why I enjoy working in a mature environment". .NET just happens to be my experience.

The point I was trying to make is that you shouldn't be print debugging in 2024.

Unfortunately it is not always possible to debug for a myriad of reasons

Yawn. I’m all but certain that all the environments in these “print debugging fail” stories have debuggers. The fact that generation after generation of programmers fall into print debugging, despite there being “no reason” to do it in many contexts for…decades at this point, should tell you that you’re missing something, not that everyone is dumb except for you.

I'm not saying people are dumb, I'm saying we've failed to provide good dev UX for debugging, so that people find it easier to reach for print debugging than leverage their debugger.

It's also clear I got the tone of my original post wrong, I was always trying to make this point, not some point scoring "I'm better because I use X".

FWIW I didn't get the feeling at all that you were trying to come off as superior because you use .NET and its debugger.

Does the GP comment claim that other languages cannot have similar quality of tooling? Why reply with a swipe?

I wish it was true

My experience in cpp is 5 times worse than in .net

I still haven’t found a good way of debugging async code that also has timing restrictions…

.., the world runs off print statements sprinkled throughout by a very frustrated and angry developer