3 ms·
Markdown gives most people >95% of the formatting they want to do. It's easy and fairly intuitive to write (most of it, anyway). It's easy to read in differen
by arp242 3y ago
Markdown gives most people >95% of the formatting they want to do.
It's easy and fairly intuitive to write (most of it, anyway).
It's easy to read in different formats and ways (HTML, plain text).
It doesn't add highly complex rendering issues. I've worked on two email clients in the last ten years, and the amount of weird HTML some send is just bonkers. Is <div style="position:fixed"> in emails crazy? Yes. Do you need to deal with it? Also yes.
- prmoustache 3y agoThe point is: markdown is HTML, not something else.
- arp242 3y agoIt's not. Markdown is markdown. It can render to HTML, but that's a different thing. I struggle to understand why this is even a point of contention.
- prmoustache 3y agoSince it supports any HTML tag, it is irrelevant. Mandate markdown and MTAs and marketing departments will send you markdown only made of pure HTML.
- arp242 3y agoThat's quite the pivot from "markdown is HTML". But no, it probably shouldn't support HTML tags, or support it with limits. And maybe also a few other things like #-headers also shouldn't be supported as it can be too easily to do by accident. All of that seems pretty obvious in all but the most aggressively pedantic reading.
- jeltz 3y agoIs C amd64 assembly then?
- prmoustache 3y agoIf your C code end up like that, yes: ``` #include <stdio.h> int main() { /* my software in ASM */ __asm__ ( [...<insert your assembly code lines here>...] ); return 0 ; } ``` And you are pretty sure this is pretty much what would happen with markdown in emails if it ended up being mandatory. You would end up with emails entirely made of html.