From: Ihor Radchenko <yantar92@gmail.com>
To: Jarmo Hurri <jarmo.hurri@iki.fi>
Cc: emacs-orgmode@gnu.org
Subject: Re: The fate of ob-asymptote.el
Date: Wed, 27 Jul 2022 11:24:22 +0800 [thread overview]
Message-ID: <87h733b5ll.fsf@localhost> (raw)
In-Reply-To: <87r12841gf.fsf@iki.fi>
Jarmo Hurri <jarmo.hurri@iki.fi> writes:
>> The advantage of maintaining ob-asymptote.el in the main asymptote
>> repo is that people who are intimately familiar with the asymptote
>> features can directly contribute and enhance the Org
>> integration. Moreover, distributing together with the asymptote means
>> no headache with back-compatibility issues.
>>
>> Maintaining on Org side will have an advantage of using the latest
>> additions to Org babel features.
>>
>> I feel like it is more important to make use of the asymptote features
>> if its devs are going to be interested. Of course, IMHO.
>
> I have a very bad feeling about tying ob-asymptote.el with Asymptote,
> and I am trying to put my finger on this feeling. I think the problem is
> this one.
>
> ob-asymptote.el is coupled very loosely with Asymptote. Basically the
> only thing ob-asymptote.el requires from Asymptote is the ability to
> call the executable with some established parameters.
>
> Then again, ob-asymptote.el is coupled much more tightly with Org. It
> uses many more properties of Org (Babel) than of the Asymptote
> program.
>
> As a result, changes in Org are much more likely to affect
> ob-asymptote.el than changes in Asymptote. I think basic software
> development rules of thumb suggest that ob-asymptote.el should then be
> bundled with Org.
From my point of view ob-asymptote.el is as bare bones as babel library
can be. It does not use any fancy Org babel features like sessions,
error display of converting the output to various :results output
options.
In contrast, it does a lot of work trying to convert Elisp types to
Asymptote in `org-babel-asymptote-var-to-asymptote`.
Of course, my view is a subject of discussion. Or maybe you have plans
to implement advanced Org babel features for Asymptote. IDK.
From my point of view, any kind of new functionality in ob-asymptote.el
requires a deep knowledge about the Asymptote programming - the
knowledge most of the Org devs lack. At the same time, changes in Org
babel core functionality are unlikely to cause any issues in
ob-asymptote - we try our best to keep backwards compatibility with
third-party babel packages anyway.
Best,
Ihor
next prev parent reply other threads:[~2022-07-27 3:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 14:55 The fate of ob-asymptote.el Jarmo Hurri
2022-07-20 15:18 ` Tory S. Anderson
2022-07-20 19:43 ` Nick Dokos
2022-07-21 5:17 ` Jarmo Hurri
2022-07-21 11:54 ` Ihor Radchenko
2022-07-21 13:21 ` Max Nikulin
2022-07-22 0:27 ` Ihor Radchenko
2022-07-22 7:12 ` Jarmo Hurri
2022-07-26 1:46 ` Ihor Radchenko
2022-07-26 10:23 ` Jarmo Hurri
2022-07-27 3:24 ` Ihor Radchenko [this message]
2022-07-27 7:31 ` Jarmo Hurri
2022-07-28 14:29 ` Ihor Radchenko
2022-07-30 9:23 ` Jarmo Hurri
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h733b5ll.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jarmo.hurri@iki.fi \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).