all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thomas Lord <lord@emf.net>
To: rms@gnu.org
Cc: "Stephen J. Turnbull" <stephen@xemacs.org>,
	bpt@tunes.org, emacs-devel@gnu.org
Subject: Re: GSoC: collaborative editing
Date: Tue, 14 Apr 2009 19:18:25 -0700	[thread overview]
Message-ID: <1239761905.6516.20.camel@dell-desktop.example.com> (raw)
In-Reply-To: <E1Ltpxp-0001ZW-N5@fencepost.gnu.org>

On Tue, 2009-04-14 at 17:14 -0400, Richard M Stallman wrote:
> Basically what you're saying is "OK, let's impose an arbitrary total
>     ordering on the changes."  Indeed that makes writing the collaborative
>     tool easier, but it also undermines collaboration by giving priority
>     to getting there *first* rather than doing it *better*.
> 
> With all due respect, I think that is a misunderstanding of the issue.
> We are talking about editing conflicts on timescales of a few seconds.
> If two people are trying to edit the same part of the text at the same
> time, they are stepping on each other's feet.  Which one does the
> stepping "better" is hardly an issue.


You still need a way to keep remote buffers in sync
and to re-sync them after temporary netsplits.
The issue Stephen is worried about is that the 
proposal offered is to ignore that problem and
assume a reliable network.   FWIW I think Stephen's
concerns are valid but that there is value in a 
short experimental project that ignores the problem
to get something basic working - at least as long
as there is some confidence that the solution to the
simpler problem stands a good chance of growing into
a solution for the more general problem.  Stephen
is right on strategy here but the offered tactic
might have some value anyway.  (Or it might not, I'm
not evaluating.)

-t







  reply	other threads:[~2009-04-15  2:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-11 20:07 GSoC: collaborative editing Brian Templeton
2009-04-12 18:02 ` Michael Albinus
2009-04-13  1:22   ` Miles Bader
2009-04-13  9:08     ` Michael Albinus
2009-04-13 14:43 ` Thien-Thi Nguyen
2009-04-13 16:11   ` Thomas Lord
2009-04-13 22:04     ` Brian Templeton
2009-04-13 22:49       ` Thomas Lord
2009-04-14  3:41         ` Brian Templeton
2009-04-14  5:24           ` Thomas Lord
2009-04-13 22:52       ` Thomas Lord
2009-04-14 10:42     ` Thien-Thi Nguyen
2009-04-15  2:03       ` Thomas Lord
2009-04-13 17:44   ` Stefan Monnier
2009-04-13 23:10     ` Richard M Stallman
2009-04-13 23:32   ` Brian Templeton
2009-04-14  3:01     ` Stephen J. Turnbull
2009-04-14  4:02       ` Brian Templeton
2009-04-14  7:29         ` Stephen J. Turnbull
2009-04-14  9:09           ` Brian Templeton
2009-04-15  2:02             ` Thomas Lord
2009-04-14 21:14       ` Richard M Stallman
2009-04-15  2:18         ` Thomas Lord [this message]
2009-04-15  1:19 ` Brian Templeton
2009-04-15  1:27   ` Brian Templeton

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=1239761905.6516.20.camel@dell-desktop.example.com \
    --to=lord@emf.net \
    --cc=bpt@tunes.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=stephen@xemacs.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.