Live data from Hacker News

Why does email development have to suck? – Explaining all the 's and 's

dodov.dev

141–150 of 183 posts

Re: Why does email development have to suck? – Explaining all the <tr>'s and <td>'s

#141
post #9
post #6

Earlier quoted context omitted.

I use mutt and unfortunately in the corporate world you can't just ignore HTML or even HTML only mails. I pipe them to elinks, works 99.9% of the time easily.

That may be the case, but that still doesn't make HTML a part of email itself. It's using email to send/receive HTML.

This is a tautology. What does the T in HTML stand for?

It’s all text if you split enough hairs.

Re: Why does email development have to suck? – Explaining all the <tr>'s and <td>'s

#142

The answer is, because Outlook is rendering your emails using Word as a browser. Only a monopoly like Microsoft could get away with that.

> Only a monopoly like Microsoft could get away with that.

What's the problem there? Unless Microsoft forces you to buy a separate Word license to use their email product, who cares if they reuse some of their own code?

Re: Why does email development have to suck? – Explaining all the <tr>'s and <td>'s

#143

Earlier quoted context omitted.

If the user can't follow basic instructions then they'll have to try again. Those users absolutely can write 'YES'. They're perfectly capable of doing so. They don't do so because they're lazy. We all know people that simply refuse to read any kind of instruction on a computer screen. They will skip past any and all prompts. Guess what? That's their problem, not yours. Stop enabling laziness!

Some businesses like to retain users, and not alienate them using obscure, hard-to use-user interfaces, and blaming the user when they get it wrong. If you can't create a way to say "yes", which is at least as easy to use as checking a checkbox and clicking a button, why should I assume you're capable of, well, much of anything. It's not that it looks unprofessional. It looks either incompetent, or deliberately obtus…

If you can't reply to an email with 'YES' then you certainly aren't smart enough to have a good enough job to pay any reasonable amount of money.

Re: Why does email development have to suck? – Explaining all the <tr>'s and <td>'s

#144

Text. Just use damn text. Nobody wants to look at your logo. Why biz people have to ruin everything.

Email is capable of having both versions of the email so the user can decide what they want. We should go back to utilizing that more.

Re: Why does email development have to suck? – Explaining all the <tr>'s and <td>'s

#145

The answer is, because Outlook is rendering your emails using Word as a browser. Only a monopoly like Microsoft could get away with that.

> Only a monopoly like Microsoft could get away with that. What's the problem there? Unless Microsoft forces you to buy a separate Word license to use their email product, who cares if they reuse some of their own code?

Because they are a monopoly, they get to ignore the HTML standards and set the defacto standard which is the subpar rendering of Word as an HTML browser.

If real competition existed senders would send modern HTML mail using CSS and Outlook would not be able to render half of it. But instead developers have to write email to the antique standards used by Word, with layout using tables and without css.

And Microsoft doesn’t care, they get away because Outlook is the monopoly.

Re: Why does email development have to suck? – Explaining all the <tr>'s and <td>'s

#146
post #136

It's HN, so I'm not surprised by the old "just send text" argument that always gets wheeled out when this topic come up, but for those not in a terminal all day there are valid reasons to format HTML emails (that don't include marketing). We send out HTML emails and reports to our users that make use of progress bars, lists, photos, colours etc and they love them. They can get quick full updates on their business wit…

Why don't you send PDFs?

The faster you get to what a user wants or has to review in an email, the more likely they’ll read it.

Re: Why does email development have to suck? – Explaining all the <tr>'s and <td>'s

#147

Earlier quoted context omitted.

Some businesses like to retain users, and not alienate them using obscure, hard-to use-user interfaces, and blaming the user when they get it wrong. If you can't create a way to say "yes", which is at least as easy to use as checking a checkbox and clicking a button, why should I assume you're capable of, well, much of anything. It's not that it looks unprofessional. It looks either incompetent, or deliberately obtus…

If you can't reply to an email with 'YES' then you certainly aren't smart enough to have a good enough job to pay any reasonable amount of money.

> Oh no, you need to find a line of text in a string that contains the word 'YES'. How incredibly difficult. Are you even a programmer? This is entirely trivial.

"Yes alright renew my subscription, just make it start in two weeks this time"

Your "solution" fails immediately here, because it gives people a false idea that they are in a dialogue with you whereas they are actually just expected to reply in a binary way.

Finding "a line of text in a string that contains the word 'YES'" is indeed trivial, however if that's all you can think of you should not be employed in any position of responsibility as it demonstrates a profound lack of judgement, understanding of how real people behave, and general business acumen.

Re: Why does email development have to suck? – Explaining all the <tr>'s and <td>'s

#148
post #9

Earlier quoted context omitted.

That may be the case, but that still doesn't make HTML a part of email itself. It's using email to send/receive HTML.

The ability to use formats other than plain text have been a standard part of email since 1992: https://datatracker.ietf.org/doc/html/rfc1341 HTML email is not merely an HTML file sent by email – it is the email.

No, is not, MIME it's like a bundled blob adjointed to a text message.

Re: Why does email development have to suck? – Explaining all the <tr>'s and <td>'s

#149

Earlier quoted context omitted.

Some businesses like to retain users, and not alienate them using obscure, hard-to use-user interfaces, and blaming the user when they get it wrong. If you can't create a way to say "yes", which is at least as easy to use as checking a checkbox and clicking a button, why should I assume you're capable of, well, much of anything. It's not that it looks unprofessional. It looks either incompetent, or deliberately obtus…

If you can't reply to an email with 'YES' then you certainly aren't smart enough to have a good enough job to pay any reasonable amount of money.

How condescending can a single software system be..? A reality check might help. Most of us write applications used not by nerds, but ordinary human beings. They don’t want to perform weird ritualistic dances just so the computer does beep-bop - ”I understood what your intention was just fine, but do it right for me!“.

Re: Why does email development have to suck? – Explaining all the <tr>'s and <td>'s

#150

The answer is, because Outlook is rendering your emails using Word as a browser. Only a monopoly like Microsoft could get away with that.

Well, that explains why, when I try to paste text into an Outlook email, I get an error "there's a problem with Word". (Then you hit Enter and paste again, which works fine.)

It's good to remember that Outlook isn't actually an email client. It was bought by Microsoft back in the days before TCP/IP became common. Outlook (still) calls messages "memos". The _first_ thing Outlook does with an RFC-compliant email is convert it into the Outlook "memo" format. There is no option to view the original email message at all. Microsoft simply bolted on a filter to deal with emails. I had hoped that the "Mail" client in Windows 10 would be a real mail user agent, but it's _worse_ than Outlook, without the excuse of predating email and being another program MS bought and rebranded.

Post reply on HN