General annoyance - arcane error descriptions

Ruby
1

As someone who writes and uses a lot of code, I have little patience for
error messages that mean something only to the person who wrote the
code. My job as a programmer is to help the user of the software
understand the nature of an error.

So when I’m writing Ruby and encounter errors such as “useless use of a
variable in void context”, it makes me crabby. Seriously, is there no
better way of helping the programmer understand the nature of their
error? I fail to see how that is any different than “you have an error,
but I’m not going to tell you what it is or help you understand the
situation”.

2

this happend if you type something you shouldn’t, the error should say a
line number, can you show me that line?

3

Hans M. wrote in post #1008633:

this happend if you type something you shouldn’t, the error should say a
line number, can you show me that line?

My point isn’t this particular example (I already rewrote the offending
code and got rid of the error).

My point is that the error itself is badly described (at least I have no
idea what “useless use of a variable in a void context” is). I fail to
understand why error messages cannot be stated in plain language, rather
than couched in terms of arcane jargon.