3 ms·
If Google really wanted to make the web fast, they would add native support for text/markdown mimetype in Chrome and ask publishers to just create .md files ins
by captn3m0 7y ago
If Google really wanted to make the web fast, they would add native support for text/markdown mimetype in Chrome and ask publishers to just create .md files instead.
- andrewshadura 7y agotext/markdown is a bad idea because it's not backwards compatible. It should be text/plain; markup=markdown, since Markdown is perfectly readable without any software support. See https://blog.freron.com/2011/thoughts-on-writing-emails-using-markdown/ https://blog.freron.com/2011/thoughts-on-writing-emails-usin... for more thoughts on this topic.
- stephenr 7y agobackwards compatible with what? In my experience anything served as `text/*` that isn’t more specifically handled (eg `text/html`) will be rendered as text/plain because the type is still `text`. Edit: rendered, not tendered
- captn3m0 7y agoThanks for the link. I get that this would help with emails, but pushing markdown into text/plain wouldn't be helpful for web content on browsers. The web already has Content Negotiation to let older clients prefer html or plain text content.