3 ms·
Maybe browsers should accept the text/markdown mimetype natively, instead of AMP. Covers 80% of the usecases, with a drastic reduction in complexity and pageloa
by captn3m0 5y ago
Maybe browsers should accept the text/markdown mimetype natively, instead of AMP. Covers 80% of the usecases, with a drastic reduction in complexity and pageload times.
- tomjen3 5y agoWhich Markdown though? Common mark, Gitlab, etc? Do we get any extensions? I like tables. HTML is not bad and it is easier to parse than markdown, the trouble is javascript and the ways ads abuse them. Strip that out, set the size of images and you can create a better experience for your users without changing all browsers. However if we can get wild requests for new content types, then I would love text/latex, so that I could create a website that fits the real size of your browser and render a gorgeous output.
- captn3m0 5y agoAccept headers can negotiate extensions I suppose, but browsers can decide what they’d like to support, same as the rest of HTML standards. In the last decade, I’ve seen browsers drop content types (FTP) and adopt media formats (WebP). But no new publication formats. If my browser can render PDF, why shouldn’t it render Markdown?