unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: A new collaborative editing package (maybe tangent)
Date: Mon, 01 Jan 2024 22:16:53 -0500	[thread overview]
Message-ID: <E1rKVGv-0007oc-DE@fencepost.gnu.org> (raw)
In-Reply-To: <87frzkdkly.fsf@posteo.net> (message from Philip Kaludercic on Sat, 30 Dec 2023 10:56:41 +0000)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > Just because it doesn't appear to be mentioned, are you familiar with
  > the CRDT package on GNU ELPA?

I'm not -- could you give us a 10 to 20 line summary of what it can do?
It would be useful to compare the two packages and see to what extent
they do and don't overlap.

If it is possible to merge the two, or extend one to have all the
capabilities of the other, that would be a significant improvement,
because we could pay the cost of one packages and get the benefits
of the two.

By the "cost" I mean the complexity of what users need to know.

On general principles, it is much better to recommend one package
to use for all activities in area A, than to recommend two packages
of which someties P is better and soetimes Q is better.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  reply	other threads:[~2024-01-02  3:16 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-30  4:22 A new collaborative editing package (maybe tangent) Yuan Fu
2023-12-30  5:28 ` Karl Fogel
2023-12-30 10:56   ` Philip Kaludercic
2024-01-02  3:16     ` Richard Stallman [this message]
2023-12-30 19:49   ` Yuan Fu
2023-12-31 15:33     ` T.V Raman
2024-01-01  4:35       ` Yuan Fu
2024-01-01 15:49   ` Richard Stallman
2024-01-02  3:54     ` Yuan Fu
2024-01-05  4:22       ` Richard Stallman
2023-12-30  8:56 ` Aw: " Arne Babenhauserheide
2023-12-30 20:09   ` Yuan Fu
2024-01-01  3:32     ` Richard Stallman
2024-01-01  4:53       ` Yuan Fu
2024-01-01 23:09         ` Stefan Kangas
2024-01-02  3:45           ` Yuan Fu
2024-01-04  3:59         ` Richard Stallman
2024-01-04  8:02           ` Dr. Arne Babenhauserheide
2024-01-05  0:33             ` Yuan Fu
2024-01-06  4:33               ` Richard Stallman
2024-01-06  7:14                 ` Yuan Fu
2024-01-08  3:48                   ` Richard Stallman
2024-01-09  2:49                     ` Richard Stallman
2024-01-06  4:33               ` Richard Stallman
2024-01-06  7:17                 ` Yuan Fu
2024-01-08  3:48                   ` Richard Stallman
2024-01-07  4:28             ` Richard Stallman
2024-01-07  4:28             ` Richard Stallman
2024-01-07  7:06               ` Yuan Fu

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1rKVGv-0007oc-DE@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    /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.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).