debugging

Another benefit of JS - since the language is interpreted, build times tend to be much lower, and debugging tends to be much easier than C++.

The syntax is grim and debugging/troubleshooting is not pleasant.

This is not my library, but it's an incredibly useful Python debugging tool which everybody should know about.

Does it have good integration with things like Peeking defintion, code lense, Debugging with watch variables/autos, etc?

Until recently debugging native plus Java was very difficult, and most of the UI stuff is in Java not native.

Not sure if there are any disadvantages with this approach (debugging?) but it's an interesting alternative.

When debugging it he found that a bunch of his local variables had weird values.

And real-time debugging and being able to set variable watches make developing much easier.

(a call, middle of debugging something nasty, etc..) Go means your kid can come in and show you the awesome thing they just drew.

If the draw is to join a risky, hot-shot, fly-by-the-seat-of-your-pants company (as it was for me), then you might be in for a reality check when you're debugging spaghetti code for 8 hours a day.

After much debugging and reading of kernel source this was all figured out, and the provider adjusted things on their end so this wouldn't happen.

I've become accustomed to Eclipse so I get auto-complete and full interactive debugging already.

Have you tried debugging things when cups doesn't "just work"?

The compiler will quite gladly let you call a `void func(unsigned x)` with -1 and let you have "fun" later debugging why who and how this function got called with an enormous value.