From: "John Wiegley" <johnw@newartisans.com>
To: emacs-devel@gnu.org
Subject: Re: Taming some chaos
Date: Fri, 16 Oct 2015 16:20:10 -0700 [thread overview]
Message-ID: <m2k2qm1jv9.fsf@newartisans.com> (raw)
In-Reply-To: <CAJnXXohZUPzRrS1rpHtgAfs1ZjZnVG9_TNt9Hbe_yHH3xOS21g@mail.gmail.com> (John Yates's message of "Wed, 14 Oct 2015 07:47:33 -0400")
>>>>> John Yates <john@yates-sheets.org> writes:
> Apart from any IDE functionality there are general weaknesses in Emacs'
> current collection of packages that I think represents a significant barrier
> to bringing in new recruits, both users and developers. I want to argue that
> most packages dabble in too many areas and are coded in too imperative a
> manner. Such shortcoming can be understood in light of the era and
> technological setting in which many Emacs conventions and paradigms were
> first developed. But that does not alter the fact that the state of
> computing / UX / what-have-you has advanced significantly.
I can't really argue with your assessment, John.
However, I think that ship has sailed. The changes you propose in your message
would require a ground-up redesign of many aspects of Emacs, would they not?
We have so much extant Emacs Lisp code, and lot of Emacs' value lies in that
code, and not merely in its fundamentals.
At this point, we can design new abstractions to be used by new code; but we
can't change how fundamental things are done in a way that suddenly makes
Emacs far less capable by breaking reams of existing code.
John
next prev parent reply other threads:[~2015-10-16 23:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 11:47 Taming some chaos John Yates
2015-10-16 15:36 ` Dmitry Gutov
2015-10-16 23:20 ` John Wiegley [this message]
2015-10-17 15:16 ` John Yates
2015-10-18 5:30 ` John Wiegley
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=m2k2qm1jv9.fsf@newartisans.com \
--to=johnw@newartisans.com \
--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 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.