Linked by Thom Holwerda on Thu 12th Apr 2012 08:59 UTC
Internet & Networking I would honestly serve at the altar of the person that did this. Keep the debugging information, but for the love of god, make your email client do something pretty and useful with it.
Permalink for comment 514018
To read all comments associated with this story, please click here.
Member since:

Your argument is so idiotic I honestly don't know how to reply. But I will make an attempt

Having something clearly pointed out is advantageous, it means I can use my brain to do much more useful things.
It kinda why they have road signs ... I get the message quickly, and allows us to concentrate on driving.

I am a Web developer, I normally do things such Web service integration. Your stance is the equivalent of saying that you shouldn't have custom error pages on a Website.

When I am developing I want proper filthy looking errors with lots of detail, when I am browsing ... I want a nice friendly message.

The resource on the client argument is also utter bullshit, my phone can render particle physics at 30 FPS in the browser. I think it can handle parsing some text.

How parsing an email message and displaying a clear and concise message to a sending failure, turned into a diatribe about how computer literacy and standards of education is utterly ridiculous.

In any case understanding the principle is more important than understanding the specifics ... parsing error messages are specifics and doesn't improve anyone's conceptual understand of how email works. It only teaches someone to pick apart a text string.

I am really fed up of geeks that seem to live in ivory CLI towers and mentally masturbate about how clever they are for understanding archaic syntax. It doesn't make you clever and those that aren't interested in reading it aren't "idiots".

It just means they have got other shit to do that they think are more important, like actually sending the email.

Edited 2012-04-13 10:24 UTC

Reply Parent Score: 1