From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs-orgmode@gnu.org
Subject: Re: Concrete suggestions to improve Org mode third-party integration :: an afterthought following Karl Voit's Orgdown proposal
Date: Mon, 6 Dec 2021 19:30:12 +0100 [thread overview]
Message-ID: <Ya5WtAe3TIWXZ/kb@maokai> (raw)
In-Reply-To: <CA+G3_PMxYVcNPsB2JrkDpmLReCc3C_aVqKdsOySshEed9t0z=A@mail.gmail.com>
On Mon, Dec 06, 2021 at 09:59:42AM -0800, Tom Gillespie wrote:
> I think it is a major strategic mistake to exclude discussions
> about interoperability from this list.
I don't think discussion on the list (or irc) is a problem. It's all
on topic if it's related to Org-mode. As you said, users and
developers share the mailing list. Just understand as an Emacs mode,
it's Emacs oriented and Emacs is the priority. The truth is Org
doesn't work outside Emacs.
The issue is when non-Emacs enhancements or feature requests are made
to the maintainers and coders. I don't think anyone is hostile to
interoperability, but hostile to additional workload.
I've watched Org since shortly after it's creation snowball features
nonstop until it burned out coders. I feel like every power user with
a new edge case feature wants it added to the Org core, and that's
just not sustainable. That's why I'm very cautious about advocating
for new features, or potential burdens external interoperability may
place on our volunteers.
> I follow this list, I keep the community up to date with my work,
> I have no idea where to look for other Org related dicussions,
IRC. #org-mode on Libera.
> Whether a certain portion of the Org community likes it or not,
> there is another portion for whom Org syntax already has a life
> beyond Org mode (e.g. academic papers and computation notebook
> style workflows).
Ideally written with Emacs, and the source blocks processed by
Emacs. I can't imagine any of the data science source blocks working
in any environment outside Emacs today.
If other programs try to replicate Org's features that's fine in the
spirit of open source, but what support do we owe their
implementations? At what point does their project impose a maintenance
burden on our volunteers? That's what we need to be careful of.
Perhaps it's worth noting the clear distinction between Org's plain
text format and the Org experience inside Emacs. I think that the
plain text format in it's simplest forms may be interpreted by
external tools (ie: README.org on Github is HTML formatted). I don't
expect any tools outside of Emacs to provide the Org editing
experience.
> The plain text nature of Org syntax and the freedom that it enables
> also means freedom from Emacs. Empowering users to own and control
> their own data to use with their own tools is the whole point. The
> fact that this means that it works outside Emacs is a critical
> feature for many data preservation use cases.
Certainly Org is future proof because it's plain text. There's a big
difference between future proofed and openly legible versus
programming two way interoperability between Emacs and an external
tool. Just ask any synchronization tool. ;]
In summary, don't assume hostility to interoperability. Please respect
the limited time of our coders and maintainers, and the additional
burdens on them that may be implied by supporting external programs.
------------------------------------------------------------------
Russell Adams RLAdams@AdamsInfoServ.com
PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/
Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
next prev parent reply other threads:[~2021-12-06 18:32 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 7:35 Concrete suggestions to improve Org mode third-party integration :: an afterthought following Karl Voit's Orgdown proposal Ihor Radchenko
2021-12-05 9:16 ` Juan Manuel Macías
2021-12-05 10:24 ` Ihor Radchenko
2021-12-05 11:08 ` Juan Manuel Macías
2021-12-05 11:54 ` Heinz Tuechler
2021-12-05 12:08 ` Ihor Radchenko
2021-12-05 13:32 ` Tim Cross
2021-12-05 13:52 ` Bruce D'Arcus
2021-12-05 22:20 ` Tim Cross
2021-12-05 14:30 ` Ihor Radchenko
2021-12-05 22:39 ` Tim Cross
2021-12-08 13:47 ` Ihor Radchenko
2021-12-08 14:39 ` Tim Cross
2021-12-08 16:16 ` Dr. Arne Babenhauserheide
2021-12-08 17:07 ` Russell Adams
2021-12-08 19:22 ` Dr. Arne Babenhauserheide
2021-12-08 20:14 ` Russell Adams
2021-12-08 21:50 ` Tim Cross
2021-12-09 8:12 ` Dr. Arne Babenhauserheide
2021-12-08 21:25 ` Tim Cross
2021-12-09 8:07 ` Dr. Arne Babenhauserheide
2021-12-09 8:36 ` Timothy
2021-12-09 9:18 ` Ihor Radchenko
2021-12-09 10:46 ` Eric S Fraga
2021-12-09 15:21 ` Russell Adams
2021-12-09 16:25 ` Eric S Fraga
2021-12-09 21:15 ` Samuel Wales
2021-12-09 23:27 ` Dr. Arne Babenhauserheide
2021-12-10 2:42 ` Tim Cross
2021-12-10 6:08 ` Dr. Arne Babenhauserheide
2021-12-11 10:03 ` Ihor Radchenko
2021-12-11 21:19 ` Tim Cross
2021-12-06 19:41 ` Karl Voit
2021-12-05 18:59 ` Juan Manuel Macías
2021-12-05 23:24 ` Russell Adams
2021-12-06 5:57 ` Juan Manuel Macías
2021-12-06 6:02 ` Timothy
2021-12-06 7:24 ` Juan Manuel Macías
2021-12-06 10:04 ` Greg Minshall
2021-12-06 14:59 ` Juan Manuel Macías
2021-12-06 17:59 ` Tom Gillespie
2021-12-06 18:25 ` M. ‘quintus’ Gülker
2021-12-06 18:42 ` Russell Adams
2021-12-06 18:47 ` Timothy
2021-12-06 19:28 ` Russell Adams
2021-12-06 19:34 ` Timothy
2021-12-06 18:30 ` Russell Adams [this message]
2021-12-06 19:10 ` Gerry Agbobada
2021-12-08 12:56 ` Ihor Radchenko
2021-12-06 10:08 ` Greg Minshall
2021-12-06 19:45 ` Karl Voit
2021-12-07 11:08 ` Vincent Breton
2021-12-08 13:13 ` Ihor Radchenko
2021-12-08 13:30 ` Ihor Radchenko
2021-12-05 13:06 ` Tim Cross
2021-12-05 14:55 ` Ihor Radchenko
2021-12-05 18:54 ` Timothy
2021-12-06 11:08 ` Max Nikulin
2021-12-06 18:43 ` Russell Adams
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=Ya5WtAe3TIWXZ/kb@maokai \
--to=rladams@adamsinfoserv.com \
--cc=emacs-orgmode@gnu.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.
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).