emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Arthur Miller <arthur.miller@live.com>
Cc: Christopher Dimech <dimech@gmx.com>, emacs-orgmode@gnu.org
Subject: Re: The fate of ditaa.jar (9.4.5.)
Date: Tue, 11 May 2021 22:53:30 +0200	[thread overview]
Message-ID: <87h7j9hu0l.fsf@web.de> (raw)
In-Reply-To: <AM9PR09MB49771EBA5C1F40E5468774E296539@AM9PR09MB4977.eurprd09.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1424 bytes --]


Arthur Miller <arthur.miller@live.com> writes:

> Christopher Dimech <dimech@gmx.com> writes:
>
>> If org-mode wants to support ditaa, it is a requirement to inform the user how to
>> get the software and install it.  Moving into into a separate repository without
>> appropriately telling the user introduces the problem that users will miss out
>> on free software that they would otherwise have used.  Using org should not be made 
>> more difficult than it already is. 
>>   
> Another problem I didn't mention in previous replay, is that user can
> have wrong (outdated) version of Java installed on his/her machine which
> might not be compatible with ditaa version org mode ships, which may
> introduce further questions and problems. IMO I think it is better to
> leave out 3rd party applications and let users install those on their
> own. 

The old version should just keep working. It requires a Java older than
Java 8, and Java 8 is available everywhere.

For the new releases that is less clear, since ditaa is adding Clojure.

I would bundle the old version to keep old documents working (I do not
want org-mode to be volatile software[1] that breaks existing documents
with an update), but notify the user that a new version exists.

[1]: https://stevelosh.com/blog/2012/04/volatile-software/

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein
ohne es zu merken

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]

  reply	other threads:[~2021-05-11 20:54 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10 11:28 Jarmo Hurri
2021-05-10 11:50 ` Eric S Fraga
2021-05-10 12:28 ` Russell Adams
2021-05-10 17:07   ` Dr. Arne Babenhauserheide
2021-05-10 20:49     ` Arthur Miller
2021-05-11  1:22       ` Christopher Dimech
2021-05-11 18:56         ` Arthur Miller
2021-05-11 20:53           ` Dr. Arne Babenhauserheide [this message]
2021-05-12  8:44             ` Arthur Miller
2021-05-12  9:41               ` Dr. Arne Babenhauserheide
2021-05-12 14:51                 ` Russell Adams
2021-05-13 12:44                 ` Jarmo Hurri
2021-05-13 14:06                   ` Arthur Miller
2021-05-13 20:08                     ` Dr. Arne Babenhauserheide
2021-05-14  1:13                       ` Arthur Miller
2021-05-14  5:30                         ` Dr. Arne Babenhauserheide
2021-05-14  5:39                           ` Christopher Dimech
2021-05-14 11:23                             ` Arthur Miller
2021-05-14 11:57                               ` Christopher Dimech
2021-05-10 18:41 ` Nick Dokos
2021-05-11  1:25   ` Christopher Dimech
2021-05-11  4:33   ` Tim Cross
2021-05-11  6:35     ` Dr. Arne Babenhauserheide
2021-05-11  6:53       ` he " Christopher Dimech
2021-05-11  8:36       ` The " Tim Cross
2021-05-11 12:52         ` TEC
2021-05-11 19:15           ` Arthur Miller
2021-05-12  0:06           ` Tim Cross
2021-05-12  8:47             ` Arthur Miller
2021-05-15 17:31           ` [External] : " Daniel Ortmann
2021-05-11 19:02       ` Arthur Miller
2021-05-16 12:19 ` Bastien

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=87h7j9hu0l.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=arthur.miller@live.com \
    --cc=dimech@gmx.com \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: The fate of ditaa.jar (9.4.5.)' \
    /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

Code repositories for project(s) associated with this 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).