Jetbrains IDEs are just as good as Visual studio. As is XCode, QT creator and friends.
And they work with many languages.
I know it's a problem with Python and Node though.
I know it's a problem with Python and Node though.
Using print is a sign tooling isn't up for the task. Not necessarily inexperience.
This. For application developers, if your users aren't taking advantage of features in your software, it's a sign the features either aren't actually better, or aren't intuitive enough to gain traction. It's a tell that you still have work to do.
I don't see why the same arguments wouldn't also apply to tools for developers like debuggers. Just because your userbase is more technically savvy doesn't mean you shouldn't care about ease of use.
In my opinion printing or logging is much more useful than debugging when you want to be able to understand the sequence of events leading up to a bug, where the debugger isn't very strong. After analyzing the logs, using conditional breakpoints depending on each other can help you catch the issue live.
Each tool has their strength and weakness, but I would never go so far as to say that debuggers are pointless. Being able to inspect memory and browse for inconsistencies can be priceless.
In fact, I often use pdb anyway because it is sometime just quicker to run, and the code execute faster under it. Also, being able to execute any python code in a shell like env is super nice, and the concept of having commands instead of looking for a button has the same pros/cons than the cli.
Do these support edit and continue?
Last I played with XCode, it didn't.
Major flaw.
While at it, you can also change the value of any visible variable and evaluate any expression in the context of the currently executing scope.
Both edit variable and hot reload code.