public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Alex Shaw <alex.shaw.as-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: What if pandoc were rewritten today?
Date: Thu, 30 Sep 2021 04:51:42 -0700 (PDT)	[thread overview]
Message-ID: <1784a254-0585-4f1f-a3b9-e8331fdcac1fn@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1219 bytes --]

Hello. This is my first post, so I apologize if I'm doing anything wrong.

I have a question/topic for conversation for John MacFarlane and any other 
long-time pandoc contributors:

*If you were to start over from scratch today, what would you do 
differently?*

If pandoc were never invented back in 2006, what are some different choices 
you would make today?
Would you use a different language (C++, Rust, Python)?
Different Haskell features (prefer Functors over Monads)?
Internal design architecture (completely re-written AST)?
Source-code structure (merge readers and writers so that each file format 
is specified in a single module instead of each file format being partially 
duplicated in a reader and a writer implementation)?

Those are all just examples. Feel free to share whatever you like.

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/1784a254-0585-4f1f-a3b9-e8331fdcac1fn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 1640 bytes --]

             reply	other threads:[~2021-09-30 11:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30 11:51 Alex Shaw [this message]
     [not found] ` <1784a254-0585-4f1f-a3b9-e8331fdcac1fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-10-01 16:16   ` John MacFarlane

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=1784a254-0585-4f1f-a3b9-e8331fdcac1fn@googlegroups.com \
    --to=alex.shaw.as-re5jqeeqqe8avxtiumwx3w@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).