Some email clients and email marketing groups have popularized email usage patters which are considered poor form for developer emails, technical emails, or on mailing lists.
Many email clients compose emails with HTML, enabling rich text formatting. Rich text formatting hinders development-oriented email conversations as it can break simple tasks like copy-pasting code snippets.
HTML emails are mainly used for marketing (or to include tracking pixels, i.e. special images hosted on a server that tracks information about the receiver upon loading them). HTML emails are one of the most common vectors for phishing, they're less accessible, and they're viewed inconsistently among receivers.
If you're sending an email, consider preferring plaintext. If you're sending a technical email or an email concerning programming, you should very strongly prefer plaintext.
For more on plaintext email, see useplaintext.email.
Leave a comment
Info on how to comment
To make a comment, please send an email using the button below. Your email address won't be shared (unless you include it in the body of your comment). If you don't want your real name to be used next to your comment, please specify the name you would like to use. If you want your name to link to a particular url, include that as well.
bold, italics, and plain text are allowed in
comments. A reasonable subset of markdown is supported, including lists,
links, and fenced code blocks. In addition, math can be formatted using
$(inline math)$ or
$$(your display equation)$$.
Please use plaintext email when commenting. See Plaintext Email and Comments on this site for more. Note also that comments are expected to be open, considerate, and respectful.
Comment via email