unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Colascione <dancol@dancol.org>, Chong Yidong <cyd@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Project systems (again)
Date: Fri, 18 Apr 2014 11:49:45 +0300	[thread overview]
Message-ID: <83r44vggye.fsf@gnu.org> (raw)
In-Reply-To: <5350DB3E.3030803@dancol.org>

> Date: Fri, 18 Apr 2014 00:58:54 -0700
> From: Daniel Colascione <dancol@dancol.org>
> CC: emacs-devel@gnu.org
> 
> > I see your point.  However, EDE was added to Emacs with the intent
> > that it serves as basis for developing features such as what you have
> > in mind.  If there's a reasonably practical way of basing your project
> > on EDE, I think we should explore that possibility first, even if it
> > requires more work on the EDE infrastructure side, because not doing
> > so would waste the effort of integrating EDE into Emacs.
> 
> I was afraid of an argument of this form --- it's just the sunken costs
> fallacy, isn't it?

It is only a fallacy if the decision to include EDE was mistaken.

> The fact that effort has been put into EDE shouldn't influence our
> evaluations of present alternatives.

Indeed, it shouldn't.  But EDE is one such alternative, and IMO we
should give some weight to past decisions, because AFAIK they are
generally taken after some careful consideration.  IOW, we should not
discard them without discussing and re-evaluating them.

> I don't think using EDE as a base would reduce the amount of needed
> work. I actually think it would increase it.

If you are right that using EDE increases the amount of work, then I
think we should remove EDE from Emacs, because it would be just
ballast then.  But I suggest to hear from the EDE developers, and
hopefully also from Chong (CC'ed), who AFAIR worked on including EDE,
before we reach such conclusions.



  reply	other threads:[~2014-04-18  8:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-17 21:52 Project systems (again) Daniel Colascione
2014-04-18  6:37 ` Eli Zaretskii
2014-04-18  7:07   ` Daniel Colascione
2014-04-18  7:50     ` Eli Zaretskii
2014-04-18  7:58       ` Daniel Colascione
2014-04-18  8:49         ` Eli Zaretskii [this message]
2014-04-19  1:45         ` Eric M. Ludlam
2014-04-19 14:26           ` Stefan Monnier
2014-04-19 19:37             ` Eric M. Ludlam
2014-04-18 15:52     ` Stefan Monnier
2014-04-18 18:37     ` Alex Ott
2014-04-18 14:03   ` Dmitry Gutov
2014-04-19  8:55     ` Bozhidar Batsov
2014-04-19 14:28       ` Stefan Monnier
2014-04-19 16:52       ` Daniel Colascione

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=83r44vggye.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=cyd@gnu.org \
    --cc=dancol@dancol.org \
    --cc=emacs-devel@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.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).