From: David Kastrup <dak@gnu.org>
Subject: Re: Init error message
Date: 13 Mar 2003 13:44:55 +0100 [thread overview]
Message-ID: <x5znnz77w8.fsf@lola.goethe.zz> (raw)
In-Reply-To: hv_ba.110800$em1.45003@news04.bloor.is.net.cable.rogers.com
Le Wang <lewang(at@)yahoo.com> writes:
> >Kevin Reeder wrote:
>
> > On Wed, 12 Mar 2003 18:14:10 -0800, Le Wang wrote:
> >
> >> XEmacs is a fine emacs. Use what you want. But PLEASE don't go
> >> out of your way to antagonize people.
> >
> > I'm puzzled by this last remark not only because the newsgroup is
> > titled GNU.emacs.help but also I'm wary of the delicate feelings
> > connected with peoples' relationship with their editor and chose
> > my words carefully.
>
> I have "delicate" feelings about both my emacsen. I think there are
> plenty of people in the same boat. It's in my (and our) interest to
> see both efforts continue and thrive.
No. It is very much against anybody's interest to see both efforts
continue and thrive separately.
There are some matters that are better implemented in one version,
and some matters that are nicer in the other. There are some things
that are better documented in one, and some that are better in the
other.
Any programmer for serious applications needs to cater for both
Emacsen. That means that he always has to program for the worst API
in addition to the better API, and with the worst documentation from
both Emacsen. This takes even more time and effort than if he was
merely stuck with the worst from both Emacsen: programming for an
additional API means additional work even if that additional API might
be better and better documented, too (which it more often than not is
not).
If there was a completely different mindshare involved (like
KDE/Qt/C++ vs GNOME/Gtk/C), applications would simply exist and be
developed independent for both Emacsen. But as it is, important
applications have to be made to run under both. And every nontrivial
Emacs project has at least man-months of work wasted on the Emacs
Schisma.
I am not interested in assigning blame, and everybody will tell me
his point of the story and how he is the good guy and the other the
bad one, but I am not interested.
I am just not going to swallow the lie that it is in the very best
interest of all that every Emacs developer with nontrivial projects
has to jump through all sorts of hoops to cater for two incarnations
of Emacs.
I don't see this change in my life time, but I am not going to applaud
it. It's wasting my time as a free software developer, similarly
like catering for Windows ports does. One does it in order not to
cut a substantial user base off, but there is no fun in it.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2003-03-13 12:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 7:29 Init error message Kevin Reeder
2003-03-11 8:44 ` John Paul Wallington
2003-03-12 0:08 ` Kevin Reeder
2003-03-12 2:19 ` Kevin Rodgers
2003-03-12 14:36 ` Kai Großjohann
2003-03-13 14:21 ` kgold
2003-03-11 14:27 ` LLeweLLyn
2003-03-12 21:58 ` Kevin Reeder
2003-03-13 2:14 ` Unknown
2003-03-13 7:53 ` Kevin Reeder
2003-03-13 12:06 ` Unknown
2003-03-13 12:44 ` David Kastrup [this message]
2003-03-13 13:00 ` John Paul Wallington
2003-03-13 14:03 ` David Kastrup
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=x5znnz77w8.fsf@lola.goethe.zz \
--to=dak@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.
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).