New ask Hacker News story: Ask HN: Markdown in Web Browser
Ask HN: Markdown in Web Browser
2 by x14km2d | 1 comments on Hacker News.
I've been researching for a few days now and in most web browsers[1] Markdown doesn't seem to be parsed. There are addons everywhere, but I don't want to install them. Since I am not a web developer, my question is if there is a specific reason for this. I actually only see advantages if websites could offer the well known .html but also .md files as format and that can be parsed right in the browser (with e.g. Github flavor). I am specifically concerned with how to save the step of parsing on my own system. For a small website this works quite well if I have e.g. only a hundred .md files, but for e.g. 5K it does get slower. Also I see the advantage as Markdown produces much smaller files. For a large project it doesn't matter, but if I have a small home server with solar power, I want to be more economical with my resources, right? My question specifically is: is there a specific reason why current web browsers don't offer an in-house Markdown parser, and what are the specific advantages/disadvantages that I may have overlooked in my consideration. [1] Tested on a Linux system. I did not test Google and Brave due to privacy concerns. Safari also falls out and so does Microsoft Edge.
2 by x14km2d | 1 comments on Hacker News.
I've been researching for a few days now and in most web browsers[1] Markdown doesn't seem to be parsed. There are addons everywhere, but I don't want to install them. Since I am not a web developer, my question is if there is a specific reason for this. I actually only see advantages if websites could offer the well known .html but also .md files as format and that can be parsed right in the browser (with e.g. Github flavor). I am specifically concerned with how to save the step of parsing on my own system. For a small website this works quite well if I have e.g. only a hundred .md files, but for e.g. 5K it does get slower. Also I see the advantage as Markdown produces much smaller files. For a large project it doesn't matter, but if I have a small home server with solar power, I want to be more economical with my resources, right? My question specifically is: is there a specific reason why current web browsers don't offer an in-house Markdown parser, and what are the specific advantages/disadvantages that I may have overlooked in my consideration. [1] Tested on a Linux system. I did not test Google and Brave due to privacy concerns. Safari also falls out and so does Microsoft Edge.
Comments
Post a Comment