Benchmark: Long Text Markdown Performance Comparison

HTML Preparation code:

<script type="text/javascript" src="https://unpkg.com/marked@1.1.0/marked.min.js"></script>
<script type="text/javascript" src="https://unpkg.com/commonmark@0.29.1/dist/commonmark.min.js"></script>
<script type="text/javascript" src="https://unpkg.com/markdown-it@11.0.0/dist/markdown-it.min.js"></script>
<script type="text/javascript" src="https://unpkg.com/remarkable@2.0.1/dist/remarkable.min.js"></script>
<script type="text/javascript" src="https://unpkg.com/micromarkdown@0.3.0/dist/micromarkdown.min.js"></script>
<script type="text/javascript" src="https://unpkg.com/snarkdown@1.2.2/dist/snarkdown.umd.js"></script>
<script type="text/javascript" src="https://lukeuser.cacus.feralhosting.com/markdown.js"></script>
<script type="text/javascript" src="https://lukeuser.cacus.feralhosting.com/markdown.altw.js"></script>

Script Preparation code:

var conv = {
    marked: marked,
    cm: new commonmark.HtmlRenderer(),
    mdit: markdownit({
        html: true
    }),
    remarkable: new remarkable.Remarkable(),
    micromarkdown: window.micromarkdown,
    snarkdown: window.snarkdown,
    markdown: window.markdown,
    markdownaltw: window.markdownaltw
};

var pars = {
    cm: new commonmark.Parser()
};

function md() {
return '# The Static, Static Blog Generator\n\n### May 17th, 2014\n\nWe all like publishing our thoughts online - but why is it such a bother to run a CMS?\n\nManaging databases, updating software, and keeping track of our content often cuts into the most important activity: *expressing ourselves*.\n\nThe web makes it really easy to share our thoughts with millions of individuals from around the world. With it we are able to talk about the things we love.\n\nOnline publishing platform have a problem though - they require certain software to be installed on web servers in order to work. This often means running your own server or paying someone else who will setup the required parts for you.\n\nAfter you setup the system, constant updates are required to make sure that any bugs in the software you are running are patched immediately to prevent your site from being hacked. This often means having a recent backup of your database ready at all times.\n\n## Can\'t we simplify? \n\nBecause running websites and managing databases isn\'t always worth the effort, "Static Content Generators" like [Dr. jekyll](http://jekyllrb.com/) and [Mr. Hyde](http://hyde.github.io/) have begun to gain traction as people pre-build websites and then place the static HTML results onto their server. \n\nThis means the web server doesn\'t need to be configured with any special software or databases - it simply serves the generated static HTML files.\n\nHowever, you still have to install the generator and setup a "build" process of sorts after every article.\n\n## Meet Jr.\n\n`Jr` is a truly *static*, static content generator. All the processing of your files happens on the requesting client\'s computer as needed. The whole system is written in client-side JavaScript. This means:\n\n- minimal bandwidth requirements\n- better search engine indexing\n- awesome screen reader support\n- *zero* security vulnerabilities\n- and more!\n\nHowever, the neatest thing about `Jr` is that you don\'t have to configure, setup, or install _anything_! Simply download the files, create your articles, and upload everything to your server!\n\ndone.\n\n## GIT thee hence\n\nIf you want to be really awesome you can use `Jr` along with the ever useful *version-control* system [git](https://help.github.com/articles/set-up-git). This allows you to keep better track of changes insuring that you can always rollback your text to recover previous versions - very handy if you work with a team!\n\n## What About Markup?\n\nLike most systems, you can compose pages in `Jr` using the text-to-HTML format "[markdown](http://daringfireball.net/projects/markdown/)". You can also use plain HTML if you want.\n\n\n## Getting Started\n\n1. [Download](http://github.com/Xeoncross/Jr) `Jr`\n2. Make your `[article-name].html` files\n3. Paste the following code at the bottom of each page:  \n	<code>&lt;script src=&quot;jr.js&quot;&gt;&lt;/script&gt;</code>  \n\n[enable HTML to render MarkDown]: <pre>\n\n![masthead](http://lorempixel.com/1000/300/)\n\n# Welcome to Jr!\n\nA static, static content generator that moves the "generator" part to the browser.\nThis site is pure text files with a single Javascript included on each page that renders\nthe theme and assets as needed.\n\nGo ahead, take a look at the source code for this page.\n\n	You want my page, fine, you render it! \n	                                   ~ Nginx\n\n\nYou see, there is really no need for the server to generate anything for simple\narticle-based sites like this. If the user wants to read your blog, they can spend\na few processor cycles to render the page themselves.\n\n[gist:c5d5244d89caa0775d92]\n\n# Jr. is open source software\n\nFor the love of bacon, [fork this project](https://github.com/Xeoncross/Jr) and add to it! &#9825;\n\n	This work \'as-is\' I provide.\n	No warranty express or implied.\n	  For no purpose fit,\n	  not even a wee bit.\n	Liability for damages denied.\n\n	Permission is granted hereby,\n	to copy, share, and modify.\n	  Use it with glee,\n	  for profit or free.\n	On this notice, these rights rely.\n\n## The MIT License (MIT)\n\nCopyright (c) 2014 David Pennington <davidpennington.me>\n\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: \n\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. \n\n\n\nOnce you have created your pages then simply upload the system to your website and enjoy.\n\n*P.S. Looking for a static social lifestream application? Checkout [MicroStream](https://github.com/Xeoncross/microstream).*\n\n![kitten](http://placekitten.com.s3.amazonaws.com/homepage-samples/408/287.jpg "obligatory kitten image")\n\n# The Static, Static Blog Generator\n\n### May 17th, 2014\n\nWe all like publishing our thoughts online - but why is it such a bother to run a CMS?\n\nManaging databases, updating software, and keeping track of our content often cuts into the most important activity: *expressing ourselves*.\n\nThe web makes it really easy to share our thoughts with millions of individuals from around the world. With it we are able to talk about the things we love.\n\nOnline publishing platform have a problem though - they require certain software to be installed on web servers in order to work. This often means running your own server or paying someone else who will setup the required parts for you.\n\nAfter you setup the system, constant updates are required to make sure that any bugs in the software you are running are patched immediately to prevent your site from being hacked. This often means having a recent backup of your database ready at all times.\n\n## Can\'t we simplify? \n\nBecause running websites and managing databases isn\'t always worth the effort, "Static Content Generators" like [Dr. jekyll](http://jekyllrb.com/) and [Mr. Hyde](http://hyde.github.io/) have begun to gain traction as people pre-build websites and then place the static HTML results onto their server. \n\nThis means the web server doesn\'t need to be configured with any special software or databases - it simply serves the generated static HTML files.\n\nHowever, you still have to install the generator and setup a "build" process of sorts after every article.\n\n## Meet Jr.\n\n`Jr` is a truly *static*, static content generator. All the processing of your files happens on the requesting client\'s computer as needed. The whole system is written in client-side JavaScript. This means:\n\n- minimal bandwidth requirements\n- better search engine indexing\n- awesome screen reader support\n- *zero* security vulnerabilities\n- and more!\n\nHowever, the neatest thing about `Jr` is that you don\'t have to configure, setup, or install _anything_! Simply download the files, create your articles, and upload everything to your server!\n\ndone.\n\n## GIT thee hence\n\nIf you want to be really awesome you can use `Jr` along with the ever useful *version-control* system [git](https://help.github.com/articles/set-up-git). This allows you to keep better track of changes insuring that you can always rollback your text to recover previous versions - very handy if you work with a team!\n\n## What About Markup?\n\nLike most systems, you can compose pages in `Jr` using the text-to-HTML format "[markdown](http://daringfireball.net/projects/markdown/)". You can also use plain HTML if you want.\n\n\n## Getting Started\n\n1. [Download](http://github.com/Xeoncross/Jr) `Jr`\n2. Make your `[article-name].html` files\n3. Paste the following code at the bottom of each page:  \n	<code>&lt;script src=&quot;jr.js&quot;&gt;&lt;/script&gt;</code>  \n\n[enable HTML to render MarkDown]: <pre>\n\n![masthead](http://lorempixel.com/1000/300/)\n\n# Welcome to Jr!\n\nA static, static content generator that moves the "generator" part to the browser.\nThis site is pure text files with a single Javascript included on each page that renders\nthe theme and assets as needed.\n\nGo ahead, take a look at the source code for this page.\n\n	You want my page, fine, you render it! \n	                                   ~ Nginx\n\n\nYou see, there is really no need for the server to generate anything for simple\narticle-based sites like this. If the user wants to read your blog, they can spend\na few processor cycles to render the page themselves.\n\n[gist:c5d5244d89caa0775d92]\n\n# Jr. is open source software\n\nFor the love of bacon, [fork this project](https://github.com/Xeoncross/Jr) and add to it! &#9825;\n\n	This work \'as-is\' I provide.\n	No warranty express or implied.\n	  For no purpose fit,\n	  not even a wee bit.\n	Liability for damages denied.\n\n	Permission is granted hereby,\n	to copy, share, and modify.\n	  Use it with glee,\n	  for profit or free.\n	On this notice, these rights rely.\n\n## The MIT License (MIT)\n\nCopyright (c) 2014 David Pennington <davidpennington.me>\n\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: \n\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. \n\n\n\nOnce you have created your pages then simply upload the system to your website and enjoy.\n\n*P.S. Looking for a static social lifestream application? Checkout [MicroStream](https://github.com/Xeoncross/microstream).*\n\n![kitten](http://placekitten.com.s3.amazonaws.com/homepage-samples/408/287.jpg "obligatory kitten image")\n\n# The Static, Static Blog Generator\n\n### May 17th, 2014\n\nWe all like publishing our thoughts online - but why is it such a bother to run a CMS?\n\nManaging databases, updating software, and keeping track of our content often cuts into the most important activity: *expressing ourselves*.\n\nThe web makes it really easy to share our thoughts with millions of individuals from around the world. With it we are able to talk about the things we love.\n\nOnline publishing platform have a problem though - they require certain software to be installed on web servers in order to work. This often means running your own server or paying someone else who will setup the required parts for you.\n\nAfter you setup the system, constant updates are required to make sure that any bugs in the software you are running are patched immediately to prevent your site from being hacked. This often means having a recent backup of your database ready at all times.\n\n## Can\'t we simplify? \n\nBecause running websites and managing databases isn\'t always worth the effort, "Static Content Generators" like [Dr. jekyll](http://jekyllrb.com/) and [Mr. Hyde](http://hyde.github.io/) have begun to gain traction as people pre-build websites and then place the static HTML results onto their server. \n\nThis means the web server doesn\'t need to be configured with any special software or databases - it simply serves the generated static HTML files.\n\nHowever, you still have to install the generator and setup a "build" process of sorts after every article.\n\n## Meet Jr.\n\n`Jr` is a truly *static*, static content generator. All the processing of your files happens on the requesting client\'s computer as needed. The whole system is written in client-side JavaScript. This means:\n\n- minimal bandwidth requirements\n- better search engine indexing\n- awesome screen reader support\n- *zero* security vulnerabilities\n- and more!\n\nHowever, the neatest thing about `Jr` is that you don\'t have to configure, setup, or install _anything_! Simply download the files, create your articles, and upload everything to your server!\n\ndone.\n\n## GIT thee hence\n\nIf you want to be really awesome you can use `Jr` along with the ever useful *version-control* system [git](https://help.github.com/articles/set-up-git). This allows you to keep better track of changes insuring that you can always rollback your text to recover previous versions - very handy if you work with a team!\n\n## What About Markup?\n\nLike most systems, you can compose pages in `Jr` using the text-to-HTML format "[markdown](http://daringfireball.net/projects/markdown/)". You can also use plain HTML if you want.\n\n\n## Getting Started\n\n1. [Download](http://github.com/Xeoncross/Jr) `Jr`\n2. Make your `[article-name].html` files\n3. Paste the following code at the bottom of each page:  \n	<code>&lt;script src=&quot;jr.js&quot;&gt;&lt;/script&gt;</code>  \n\n[enable HTML to render MarkDown]: <pre>\n\n![masthead](http://lorempixel.com/1000/300/)\n\n# Welcome to Jr!\n\nA static, static content generator that moves the "generator" part to the browser.\nThis site is pure text files with a single Javascript included on each page that renders\nthe theme and assets as needed.\n\nGo ahead, take a look at the source code for this page.\n\n	You want my page, fine, you render it! \n	                                   ~ Nginx\n\n\nYou see, there is really no need for the server to generate anything for simple\narticle-based sites like this. If the user wants to read your blog, they can spend\na few processor cycles to render the page themselves.\n\n[gist:c5d5244d89caa0775d92]\n\n# Jr. is open source software\n\nFor the love of bacon, [fork this project](https://github.com/Xeoncross/Jr) and add to it! &#9825;\n\n	This work \'as-is\' I provide.\n	No warranty express or implied.\n	  For no purpose fit,\n	  not even a wee bit.\n	Liability for damages denied.\n\n	Permission is granted hereby,\n	to copy, share, and modify.\n	  Use it with glee,\n	  for profit or free.\n	On this notice, these rights rely.\n\n## The MIT License (MIT)\n\nCopyright (c) 2014 David Pennington <davidpennington.me>\n\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: \n\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. \n\n\n\nOnce you have created your pages then simply upload the system to your website and enjoy.\n\n*P.S. Looking for a static social lifestream application? Checkout [MicroStream](https://github.com/Xeoncross/microstream).*\n\n![kitten](http://placekitten.com.s3.amazonaws.com/homepage-samples/408/287.jpg "obligatory kitten image")\n\n# The Static, Static Blog Generator\n\n### May 17th, 2014\n\nWe all like publishing our thoughts online - but why is it such a bother to run a CMS?\n\nManaging databases, updating software, and keeping track of our content often cuts into the most important activity: *expressing ourselves*.\n\nThe web makes it really easy to share our thoughts with millions of individuals from around the world. With it we are able to talk about the things we love.\n\nOnline publishing platform have a problem though - they require certain software to be installed on web servers in order to work. This often means running your own server or paying someone else who will setup the required parts for you.\n\nAfter you setup the system, constant updates are required to make sure that any bugs in the software you are running are patched immediately to prevent your site from being hacked. This often means having a recent backup of your database ready at all times.\n\n## Can\'t we simplify? \n\nBecause running websites and managing databases isn\'t always worth the effort, "Static Content Generators" like [Dr. jekyll](http://jekyllrb.com/) and [Mr. Hyde](http://hyde.github.io/) have begun to gain traction as people pre-build websites and then place the static HTML results onto their server. \n\nThis means the web server doesn\'t need to be configured with any special software or databases - it simply serves the generated static HTML files.\n\nHowever, you still have to install the generator and setup a "build" process of sorts after every article.\n\n## Meet Jr.\n\n`Jr` is a truly *static*, static content generator. All the processing of your files happens on the requesting client\'s computer as needed. The whole system is written in client-side JavaScript. This means:\n\n- minimal bandwidth requirements\n- better search engine indexing\n- awesome screen reader support\n- *zero* security vulnerabilities\n- and more!\n\nHowever, the neatest thing about `Jr` is that you don\'t have to configure, setup, or install _anything_! Simply download the files, create your articles, and upload everything to your server!\n\ndone.\n\n## GIT thee hence\n\nIf you want to be really awesome you can use `Jr` along with the ever useful *version-control* system [git](https://help.github.com/articles/set-up-git). This allows you to keep better track of changes insuring that you can always rollback your text to recover previous versions - very handy if you work with a team!\n\n## What About Markup?\n\nLike most systems, you can compose pages in `Jr` using the text-to-HTML format "[markdown](http://daringfireball.net/projects/markdown/)". You can also use plain HTML if you want.\n\n\n## Getting Started\n\n1. [Download](http://github.com/Xeoncross/Jr) `Jr`\n2. Make your `[article-name].html` files\n3. Paste the following code at the bottom of each page:  \n	<code>&lt;script src=&quot;jr.js&quot;&gt;&lt;/script&gt;</code>  \n\n[enable HTML to render MarkDown]: <pre>\n\n![masthead](http://lorempixel.com/1000/300/)\n\n# Welcome to Jr!\n\nA static, static content generator that moves the "generator" part to the browser.\nThis site is pure text files with a single Javascript included on each page that renders\nthe theme and assets as needed.\n\nGo ahead, take a look at the source code for this page.\n\n	You want my page, fine, you render it! \n	                                   ~ Nginx\n\n\nYou see, there is really no need for the server to generate anything for simple\narticle-based sites like this. If the user wants to read your blog, they can spend\na few processor cycles to render the page themselves.\n\n[gist:c5d5244d89caa0775d92]\n\n# Jr. is open source software\n\nFor the love of bacon, [fork this project](https://github.com/Xeoncross/Jr) and add to it! &#9825;\n\n	This work \'as-is\' I provide.\n	No warranty express or implied.\n	  For no purpose fit,\n	  not even a wee bit.\n	Liability for damages denied.\n\n	Permission is granted hereby,\n	to copy, share, and modify.\n	  Use it with glee,\n	  for profit or free.\n	On this notice, these rights rely.\n\n## The MIT License (MIT)\n\nCopyright (c) 2014 David Pennington <davidpennington.me>\n\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: \n\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. \n\n\n\nOnce you have created your pages then simply upload the system to your website and enjoy.\n\n*P.S. Looking for a static social lifestream application? Checkout [MicroStream](https://github.com/Xeoncross/microstream).*\n\n![kitten](http://placekitten.com.s3.amazonaws.com/homepage-samples/408/287.jpg "obligatory kitten image")\n\n# The Static, Static Blog Generator\n\n### May 17th, 2014\n\nWe all like publishing our thoughts online - but why is it such a bother to run a CMS?\n\nManaging databases, updating software, and keeping track of our content often cuts into the most important activity: *expressing ourselves*.\n\nThe web makes it really easy to share our thoughts with millions of individuals from around the world. With it we are able to talk about the things we love.\n\nOnline publishing platform have a problem though - they require certain software to be installed on web servers in order to work. This often means running your own server or paying someone else who will setup the required parts for you.\n\nAfter you setup the system, constant updates are required to make sure that any bugs in the software you are running are patched immediately to prevent your site from being hacked. This often means having a recent backup of your database ready at all times.\n\n## Can\'t we simplify? \n\nBecause running websites and managing databases isn\'t always worth the effort, "Static Content Generators" like [Dr. jekyll](http://jekyllrb.com/) and [Mr. Hyde](http://hyde.github.io/) have begun to gain traction as people pre-build websites and then place the static HTML results onto their server. \n\nThis means the web server doesn\'t need to be configured with any special software or databases - it simply serves the generated static HTML files.\n\nHowever, you still have to install the generator and setup a "build" process of sorts after every article.\n\n## Meet Jr.\n\n`Jr` is a truly *static*, static content generator. All the processing of your files happens on the requesting client\'s computer as needed. The whole system is written in client-side JavaScript. This means:\n\n- minimal bandwidth requirements\n- better search engine indexing\n- awesome screen reader support\n- *zero* security vulnerabilities\n- and more!\n\nHowever, the neatest thing about `Jr` is that you don\'t have to configure, setup, or install _anything_! Simply download the files, create your articles, and upload everything to your server!\n\ndone.\n\n## GIT thee hence\n\nIf you want to be really awesome you can use `Jr` along with the ever useful *version-control* system [git](https://help.github.com/articles/set-up-git). This allows you to keep better track of changes insuring that you can always rollback your text to recover previous versions - very handy if you work with a team!\n\n## What About Markup?\n\nLike most systems, you can compose pages in `Jr` using the text-to-HTML format "[markdown](http://daringfireball.net/projects/markdown/)". You can also use plain HTML if you want.\n\n\n## Getting Started\n\n1. [Download](http://github.com/Xeoncross/Jr) `Jr`\n2. Make your `[article-name].html` files\n3. Paste the following code at the bottom of each page:  \n	<code>&lt;script src=&quot;jr.js&quot;&gt;&lt;/script&gt;</code>  \n\n[enable HTML to render MarkDown]: <pre>\n\n![masthead](http://lorempixel.com/1000/300/)\n\n# Welcome to Jr!\n\nA static, static content generator that moves the "generator" part to the browser.\nThis site is pure text files with a single Javascript included on each page that renders\nthe theme and assets as needed.\n\nGo ahead, take a look at the source code for this page.\n\n	You want my page, fine, you render it! \n	                                   ~ Nginx\n\n\nYou see, there is really no need for the server to generate anything for simple\narticle-based sites like this. If the user wants to read your blog, they can spend\na few processor cycles to render the page themselves.\n\n[gist:c5d5244d89caa0775d92]\n\n# Jr. is open source software\n\nFor the love of bacon, [fork this project](https://github.com/Xeoncross/Jr) and add to it! &#9825;\n\n	This work \'as-is\' I provide.\n	No warranty express or implied.\n	  For no purpose fit,\n	  not even a wee bit.\n	Liability for damages denied.\n\n	Permission is granted hereby,\n	to copy, share, and modify.\n	  Use it with glee,\n	  for profit or free.\n	On this notice, these rights rely.\n\n## The MIT License (MIT)\n\nCopyright (c) 2014 David Pennington <davidpennington.me>\n\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: \n\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. \n\n\n\nOnce you have created your pages then simply upload the system to your website and enjoy.\n\n*P.S. Looking for a static social lifestream application? Checkout [MicroStream](https://github.com/Xeoncross/microstream).*\n\n![kitten](http://placekitten.com.s3.amazonaws.com/homepage-samples/408/287.jpg "obligatory kitten image")\n\n# The Static, Static Blog Generator\n\n### May 17th, 2014\n\nWe all like publishing our thoughts online - but why is it such a bother to run a CMS?\n\nManaging databases, updating software, and keeping track of our content often cuts into the most important activity: *expressing ourselves*.\n\nThe web makes it really easy to share our thoughts with millions of individuals from around the world. With it we are able to talk about the things we love.\n\nOnline publishing platform have a problem though - they require certain software to be installed on web servers in order to work. This often means running your own server or paying someone else who will setup the required parts for you.\n\nAfter you setup the system, constant updates are required to make sure that any bugs in the software you are running are patched immediately to prevent your site from being hacked. This often means having a recent backup of your database ready at all times.\n\n## Can\'t we simplify? \n\nBecause running websites and managing databases isn\'t always worth the effort, "Static Content Generators" like [Dr. jekyll](http://jekyllrb.com/) and [Mr. Hyde](http://hyde.github.io/) have begun to gain traction as people pre-build websites and then place the static HTML results onto their server. \n\nThis means the web server doesn\'t need to be configured with any special software or databases - it simply serves the generated static HTML files.\n\nHowever, you still have to install the generator and setup a "build" process of sorts after every article.\n\n## Meet Jr.\n\n`Jr` is a truly *static*, static content generator. All the processing of your files happens on the requesting client\'s computer as needed. The whole system is written in client-side JavaScript. This means:\n\n- minimal bandwidth requirements\n- better search engine indexing\n- awesome screen reader support\n- *zero* security vulnerabilities\n- and more!\n\nHowever, the neatest thing about `Jr` is that you don\'t have to configure, setup, or install _anything_! Simply download the files, create your articles, and upload everything to your server!\n\ndone.\n\n## GIT thee hence\n\nIf you want to be really awesome you can use `Jr` along with the ever useful *version-control* system [git](https://help.github.com/articles/set-up-git). This allows you to keep better track of changes insuring that you can always rollback your text to recover previous versions - very handy if you work with a team!\n\n## What About Markup?\n\nLike most systems, you can compose pages in `Jr` using the text-to-HTML format "[markdown](http://daringfireball.net/projects/markdown/)". You can also use plain HTML if you want.\n\n\n## Getting Started\n\n1. [Download](http://github.com/Xeoncross/Jr) `Jr`\n2. Make your `[article-name].html` files\n3. Paste the following code at the bottom of each page:  \n	<code>&lt;script src=&quot;jr.js&quot;&gt;&lt;/script&gt;</code>  \n\n[enable HTML to render MarkDown]: <pre>\n\n![masthead](http://lorempixel.com/1000/300/)\n\n# Welcome to Jr!\n\nA static, static content generator that moves the "generator" part to the browser.\nThis site is pure text files with a single Javascript included on each page that renders\nthe theme and assets as needed.\n\nGo ahead, take a look at the source code for this page.\n\n	You want my page, fine, you render it! \n	                                   ~ Nginx\n\n\nYou see, there is really no need for the server to generate anything for simple\narticle-based sites like this. If the user wants to read your blog, they can spend\na few processor cycles to render the page themselves.\n\n[gist:c5d5244d89caa0775d92]\n\n# Jr. is open source software\n\nFor the love of bacon, [fork this project](https://github.com/Xeoncross/Jr) and add to it! &#9825;\n\n	This work \'as-is\' I provide.\n	No warranty express or implied.\n	  For no purpose fit,\n	  not even a wee bit.\n	Liability for damages denied.\n\n	Permission is granted hereby,\n	to copy, share, and modify.\n	  Use it with glee,\n	  for profit or free.\n	On this notice, these rights rely.\n\n## The MIT License (MIT)\n\nCopyright (c) 2014 David Pennington <davidpennington.me>\n\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: \n\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. \n\n\n\nOnce you have created your pages then simply upload the system to your website and enjoy.\n\n*P.S. Looking for a static social lifestream application? Checkout [MicroStream](https://github.com/Xeoncross/microstream).*\n\n![kitten](http://placekitten.com.s3.amazonaws.com/homepage-samples/408/287.jpg "obligatory kitten image")\n\n'}

Tests:

Marked
conv.marked(md());
CommonMark
conv.cm.render(pars.cm.parse(md()));
Markdown-it
conv.mdit.render(md());
Remarkable
conv.remarkable.render(md());
Micromarkdown
conv.micromarkdown.parse(md(),true);
Snarkdown
conv.snarkdown(md());
markdown-wasm
try {markdown.parse(md());} catch {}
markdown-wasm-alt
try {markdownaltw.parse(md());} catch {}

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
Marked
CommonMark
Markdown-it
Remarkable
Micromarkdown
Snarkdown
markdown-wasm
markdown-wasm-alt

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated one month ago):

LLMs can make mistakes. Check important info.

Let's dive into the benchmark results!

Based on the provided data, here are some observations and comparisons between the different Markdown parsers:

1. **Remarkable**: Still leads the pack with an average of 1211.39 executions per second. This suggests that Remarkable is still a top choice for rendering Markdown.
2. **Marked**: Comes in second with an average of 1041.22 executions per second, indicating that Marked is a close contender to Remarkable.
3. **CommonMark**: With an average of 967.20 executions per second, CommonMark is still a viable option, but slightly behind the top two.
4. **Snarkdown**: Snarkdown's average execution speed is around 954.47 seconds, which is lower than Remarkable and Marked, but still respectable.
5. **Markdown-it**: Markdown-it comes in last with an average of 870.61 executions per second, indicating that it may require some tweaks or optimizations to catch up with the top parsers.
6. **Micromarkdown**: Micromarkdown's performance is the lowest among all options, with an average execution speed of around 616.34 seconds.

**Comparison and Recommendations:**

* For rendering Markdown, Remarkable and Marked are the top choices, offering fast execution speeds.
* If you're looking for a more lightweight option, CommonMark might be a suitable choice.
* Snarkdown is still a viable option, but may require some tuning to match the performance of other parsers.
* Micromarkdown's poor performance suggests that it may not be the best choice for demanding applications.

**Takeaway:**

In conclusion, if you're looking for fast Markdown rendering, Remarkable and Marked are the top choices. If you need a lightweight option, CommonMark might be worth considering. Snarkdown and Micromarkdown require some optimization to match the performance of other parsers.

Latest run results:

Run details: (Test run date: one year ago)

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/112.0

Browser/OS: Firefox 112 on Mac OS X 10.15

View result in a separate tab

Test name	Executions per second
Marked	1041.2 Ops/sec
CommonMark	967.2 Ops/sec
Markdown-it	870.6 Ops/sec
Remarkable	1211.4 Ops/sec
Micromarkdown	616.3 Ops/sec
Snarkdown	954.5 Ops/sec
markdown-wasm	581271.5 Ops/sec
markdown-wasm-alt	520617.5 Ops/sec

Related benchmarks:

Long Text Markdown Performance Comparison (version: 0)

A performance comparison of leading Javascript Markdown implementations.

Comparing performance of: Marked vs CommonMark vs Markdown-it vs Remarkable vs Micromarkdown vs Snarkdown vs markdown-wasm vs markdown-wasm-alt

Created: 3 years ago by: Guest

Jump to the latest result

Marked

CommonMark

Markdown-it

Remarkable

Micromarkdown

Snarkdown

markdown-wasm

markdown-wasm-alt

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated one month ago):