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 14:39:36 +0200	[thread overview]
Message-ID: <87wo5tgpkn.fsf@zeitkraut.de> (raw)
In-Reply-To: <a9b39338-0830-45dc-bf30-59d8de61278b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

brainchild writes:

> This observation leads me to wonder whether it is possible, at least in
> principle, to achieve a substantially smaller executable size that offers a
> specific selection of the full application's capabilities.

I had a look into this some time ago. My conclusion was: while it is
possible to arrive at a smaller executable by manually disabling all
unwanted code, it is not worth the effort.

The question usually arises with the idea of using pandoc for Markdown
parsing, outputting various other formats. Many large parsers, like
those for LaTeX and HTML, are dependencies of the Markdown reader, so
they cannot be removed. The most commonly used writers are also some of
the most complex, so there is not that much to gain there either.

I seem to remember that, even after removing a significant amount of
functionality, I still achieved only a meager 20% reduction in binary
size. More aggressive pruning should be able to squeeze out some more
percentage points, but the binary will never really be "small".

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


  parent reply	other threads:[~2020-05-03 12:39 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 [this message]
     [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
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=87wo5tgpkn.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).