public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: build customizability
Date: Sun, 03 May 2020 17:07:03 +0200	[thread overview]
Message-ID: <87v9ldgiqw.fsf@zeitkraut.de> (raw)
In-Reply-To: <459f63cf-31b3-48a4-adfe-21d5f23f9d22-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


brainchild writes:
>> Many large parsers, like those for LaTeX and HTML, are dependencies
>> of the Markdown reader
>
> This observations strikes me as quite peculiar. Would you elaborate the
> reasons for the dependencies?

HTML can always be included in Markdown, and extensions like
`markdown_in_html_blocks` make it necessary to parse it.
IIRC, LaTeX is required for math support as well as the `+raw_tex`
extension. Removing those would mean rewriting large parts of the
parser.

>> I seem to remember that, even after removing a significant amount of
>> functionality, I still achieved only a meager 20% reduction in binary
>
> Did your tests include the comprehensive elimination of unneeded library
> dependencies? Doing so correctly might be nontrivial as it requires having
> an accurate graph for dependency resolution.

No, mostly for the reason you mention, but also because the number of
packages made redundant in my experiment were countable on one hand.
That's less than 10% of total dependencies.

--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124


  parent reply	other threads:[~2020-05-03 15:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 13:57 brainchild
     [not found] ` <43e8ce91-0738-4477-bcf5-e826219d9b1d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-05-01 15:51   ` John MacFarlane
     [not found]     ` <m2wo5vy7pz.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-05-03  8:05       ` brainchild
     [not found]         ` <a9b39338-0830-45dc-bf30-59d8de61278b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-05-03 12:39           ` Albert Krewinkel
     [not found]             ` <87wo5tgpkn.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2020-05-03 12:55               ` brainchild
     [not found]                 ` <459f63cf-31b3-48a4-adfe-21d5f23f9d22-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-05-03 13:39                   ` Ivan Lazar Miljenovic
     [not found]                     ` <CA+u6gbwbuU9QhDFygzHh259Pa99qCTNBAq6-Jym6z24hhCF=PQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-05-03 14:05                       ` BPJ
2020-05-03 15:07                   ` Albert Krewinkel [this message]
2020-05-04  6:45   ` brainchild
     [not found]     ` <f9fd9cfe-e03f-45d3-bcb5-07267c28e565-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-05-04 14:47       ` Daniel Staal
     [not found]         ` <75f238b6-2ae0-2e73-66c9-54245b7cd655-Jdbf3xiKgS8@public.gmane.org>
2020-05-05  2:11           ` brainchild
2020-05-05  8:39           ` Colored text R. Wils
     [not found]             ` <CAJPsUMeBTr2BcSL8V8mQuh=50LDx+z8+547MUcMzZYqahF9CAQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-05-05  8:42               ` brainchild
2020-05-04  8:36   ` build customizability brainchild

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v9ldgiqw.fsf@zeitkraut.de \
    --to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).