I'm getting annoyed with the increasing number of platforms that implement the "Oops, something went wrong" vague error message.

Ehh, there's not gonna be anything an end user can probably do, and for your average user anything else is likely to be confusing.

error handling can be a pain in the ass so have mercy on the developer.

imagine catching some error from a method in an external library and having to parse the error message to get it down to the client.

nahh, all errors mean something happened.

There's not much you can say about a 500... You can't reveal any backend logic/structures to the FE. Especially [!!!] in the case of errors.

Do want it to read like
"Buffer overflow while processing the user-provided page field! Please exploit carefully."
or is a slightly more vague
"Sorry, we really botched this, so a bug crashed our backend!"
more to your liking?

my question would be why is everyone going down the "oopsie woopsie we fuffed up somethingy uwu" instead of stating "unexpected error. try again later. button(report issue)"

@ilechuks73 Developers shouldn't be lazy.

@netikras Hm yeah, security.

@qwwerty That would be better.

You're not alone, I hate these too. Would I rather have an error code? YES. Why? So I can search for that error code and maybe, just maybe find a solution online. With these vague, generic error messages the error could be anything and no one can help you, they're not searchable.