Hacker News Reader

Recommended practice in server frameworks is to control the information in the errors according to the environment i.e. Development|Production.

But many websites fail to do so.

You can change that in the php.ini to set the levels of Warnings/Errors to show if you want to. (And also naturally the MySQL config, to allow more connections)

But if you were the developer of this code, it's useful to pinpoint what went wrong and where.

This is a common "HN Hug-of-Death" ;)

It's to aid the developer during development. All of them provide ways to hide this in production. But most developers remain ignorant or are lazy to bother about it.

I'd assume they're optimizing for beginner developer UX, and assuming that anyone using mysql for something important will know to customize the error handling.