public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Google Summer of Code 2015
Date: Sat, 21 Feb 2015 23:06:57 -0800	[thread overview]
Message-ID: <20150222070657.GB42783@localhost.hsd1.ca.comcast.net> (raw)
In-Reply-To: <CA+u6gbw6_Z83CujqoKV36gxnr05R96f-yg51+S-im21sEY8T7g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

+++ Ivan Lazar Miljenovic [Feb 22 15 14:12 ]:
>On 22 February 2015 at 10:27, John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> wrote:
>> +++ John MacFarlane [Feb 21 15 15:15 ]:
>>>
>>> +++ Matthew Pickering [Feb 20 15 21:45 ]:
>>>>
>>>> Dear list,
>>>>
>>>> I have created a ticket on the Haskell.org GSoC idea list for one of the
>>>> ideas which John suggested[1] would be suitable. It is important that
>>>> that
>>>> projects are fairly freestanding (not requiring intimate knowledge of the
>>>> architecture) and are selected based on utility to the Haskell community
>>>> as
>>>> a whole.
>>>>
>>>> If anyone has any comments, feel free to edit the proposal or reply here
>>>> and I will make the changes.
>>>>
>>>> https://ghc.haskell.org/trac/summer-of-code/ticket/1660#ticket
>>>
>>>
>>> It's a good proposal.  Some further motivation:  pandoc's current
>>> Markdown parser is not very efficient.  It even goes exponential on some
>>> inputs, which is not good for web use.
>>>
>>> I've already developed algorithms for parsing CommonMark efficiently,
>>> without backtracking.  They are so much more efficient than what pandoc
>>> currently does that even the JavaScript implementation of commonmark is
>>> 3-4 times faster than pandoc, and the C implementation is 30-40 times
>>> faster.
>>>
>>> So I'd hope for a 10X speedup with a rewrite.
>>
>>
>> Further thoughts on this.
>>
>> The best GSOC projects benefit the whole community (infrastructure).
>>
>> So, it might make more sense to write a standalone CommonMark parser
>> library with a liberal (BSD) license, that could be used in other
>> Haskell projects (e.g., potentially, in some future version of Haddock).
>>
>> If this is made extensible, pandoc could simply use this library.
>> But the library would also be available for other purposes.
>>
>> Pandoc itself won't ever be relicensed.  But I think it would be a good
>> idea, if contributors will agree, to dual license pandoc-types BSD3/GPL.
>> (There are only a few commits by people other than me, so this is
>> feasible.)
>
>If pandoc-types is licensed BSD3, is there any real need for it to
>also be licensed GPL (especially since Cabal doesn't really understand
>dual-licensing)?

Probably not.


  parent reply	other threads:[~2015-02-22  7:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20 21:45 Matthew Pickering
     [not found] ` <CALuQ0m8oGFfhneJtng=vRtRbfZ+3Kip6x_rUDc+yxqfv_6Abpw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-21 23:15   ` John MacFarlane
     [not found]     ` <20150221231559.GG42178-bi+AKbBUZKbivNSvqvJHCtPlBySK3R6THiGdP5j34PU@public.gmane.org>
2015-02-21 23:27       ` John MacFarlane
     [not found]         ` <20150221232739.GA42324-bi+AKbBUZKbivNSvqvJHCtPlBySK3R6THiGdP5j34PU@public.gmane.org>
2015-02-22  3:12           ` Ivan Lazar Miljenovic
     [not found]             ` <CA+u6gbw6_Z83CujqoKV36gxnr05R96f-yg51+S-im21sEY8T7g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-22  7:06               ` John MacFarlane [this message]
     [not found]                 ` <20150222070657.GB42783-bi+AKbBUZKbivNSvqvJHCtPlBySK3R6THiGdP5j34PU@public.gmane.org>
2015-02-23 22:38                   ` Matthew Pickering
  -- strict thread matches above, loose matches on Subject: below --
2015-01-16  2:36 Raniere Silva
     [not found] ` <20150116023632.GZ19197-j/q8TITqDDESy/uc2pLa89BPR1lH4CV8@public.gmane.org>
2015-01-16  2:58   ` Matthew Pickering

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=20150222070657.GB42783@localhost.hsd1.ca.comcast.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@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).