Actually, I see (and write) this one fairly often and I think it's a good message: it tells the user that something is *very* wrong. Something the programmer knew shouldn't happen and this incident is 1) important and 2) should involve a code correction 2) isn't bad data or something on their end.

So, while amusing, I think it's just fine.