2

I tried to explain to our Ruby system architect that rescuing Exception (which also catches NoMemoryError) is a bad idea. I'm then told we _want_ to catch it and log who the culprit is and flash an error to the user. There's still a palm print on my face.

Comments
Add Comment