2 years ago

In the 1990s, my Mac OS 7.5.1 would generate an error like this: Why did I have to reboot? The reason was because Windows/Macintosh used a shared memory model before protected memory existed, so it was easy for an application to overwrite system memory and crash the kernel.

I’ve seen this a lot in Java code for some reason, so here it is: The problem is you get multiple errors for the same exception; it’s just ambiguous and unnecessary.

Something like this is excellent: An error like this is great, because your application can tell the user something useful.

You should write your frontend to use json stringify to parse the backend errors and return with valid context and messaging for the user.