Re: Markdown for AMP Project https://www.ampproject.org/

[support1-ZohPw8X7yHTQT0dZR+AlfA@public.gmane.org]

On Tue, May 02, 2017 at 02:09:50PM -0700, mb21 wrote:
> @Jean, you know you can specify image sizes in pandoc as well, right? see 
> http://pandoc.org/MANUAL.html#images

I see that, it is nice usable tool and I use it. I also use Pandoc to
convert HTML to text, at least temporarily, as it may show HTTP links
within the text body, which is nice feature.

Before I was using elinks browser with --dump option, and links appear
then on the bottom of the page.

However, it is not as good for my production and the website revision
system with hundreds (thousands) of markdown pages, as it is too
slow.

If I add AMP pages, that means there is double number of pages to
process. Pandoc is not thinkable for the large work, after short
review and stupid benchmark below.

time lisp -x '(loop for i from 1 to 1000 do (shell "pandoc -f markdown -t html  tmp/benchmark.md > /dev/null" ))'

NIL

real    2m30.604s
user    2m13.572s
sys     0m10.972s


time lisp -x '(loop for i from 1 to 1000 do (shell "discount_markdown tmp/benchmark.md > /dev/null" ))'
NIL

real    0m6.388s
user    0m0.060s
sys     0m0.056s

the difference should be very obvious. Discount markdown is way better
for markdown, while Pandoc is way better for general purpose
conversions and is too slow for huge collection of markdown pages.

Discount markdown: www.pell.portland.or.us/~orc/Code/discount/

Jean