The one thing worse than debugging code is debugging "types". Those 30-page C++ compiler errors are definitely worse than whatever I had to do with (for example) Python.
That's definitely in the "programming language sucks" category. Good languages make it easy to debug problems with your types.
I was responding to a comment that was suggesting letting an AI to do that.
> The one thing worse than debugging code is debugging "types".
It depends on a language. In languages with first-class types, we have the same tools to debug types. Classical C++ templates are more akin to a macro system than a type system.
C++ is sort of the canonical example of a language with a terrible type system, so it's not really the right place to look for this comparison.
Everyone complains how slowly Rust compiles. But at least its error messages are much better.
By the way, if you spend 90% of time debugging your code, I think that's really sad. Either the programming language sucks, or the codebase sucks, or both. I probably spend 10-20% max of my time on debugging.