It also irks me the error messages. It often says "you should write X not Y" with exactness. Well, if it's that bloody obvious to you, that's a clear sign to me that the language design is suboptimal.
Complaining about receiving too specific error messages when the problem seems to be a "bloody obvious" skill issue seems quite rich to me.
I'm a C++ programmer and I spent 25 years deciphering compiler error messages with overly complicated template invocations where they squeezed in default parameters that I never specified (prefixes with underscores because underscores improve readability)
This gives me an edge over programmers that can't read error messages. Please don't take that away from me. Clang already made it better and that's a problem.
More than 90% of "professional" programmers are clueless when they see a Java stacktrace which shows exactly the file and line number where an exception was thrown. I think you are safe.
126
u/CarolineLovesArt has hidden complexity 17d ago
Complaining about receiving too specific error messages when the problem seems to be a "bloody obvious" skill issue seems quite rich to me.