From: Eli Zaretskii <eliz@gnu.org>
To: John Wiegley <jwiegley@gmail.com>
Cc: emacs-devel@gnu.org, drew.adams@oracle.com, john@yates-sheets.org
Subject: Re: Casting as wide a net as possible
Date: Thu, 10 Dec 2015 21:07:43 +0200 [thread overview]
Message-ID: <83a8pi9l6o.fsf@gnu.org> (raw)
In-Reply-To: <m2d1uenn4h.fsf@newartisans.com>
> From: John Wiegley <jwiegley@gmail.com>
> Date: Thu, 10 Dec 2015 11:02:06 -0800
> Cc: Emacs developers <emacs-devel@gnu.org>, John Yates <john@yates-sheets.org>
>
> I agree. The things that make Emacs great:
>
> 1. Highly consistent syntax.
> 2. Self-documenting.
> 3. Integrated debugger.
> 4. Ability to re-evaluate functions in a running environment.
> (i.e., everything that made Lisp Machines great)
> 5. Natural syntax for scoping resources (`with-temp-buffer ...')
> 6. Large and well documented API
> 7. Stable and mature concepts evolved over decades
> 8. Huge, HUGE community of cargo-cultable examples, for those just learning
I think we should also mention the huge number of applications and
packages included or available out there. I don't think there's a
computing related job that Emacs does not already do, given the right
packages are installed.
Also, the fact that it presents more or less the same behavior on all
supported platforms (modulo some system-specific features on each
platform).
next prev parent reply other threads:[~2015-12-10 19:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 16:46 Casting as wide a net as possible (was: First draft of the Emacs website) John Yates
2015-12-10 17:31 ` Eli Zaretskii
2015-12-10 18:56 ` Drew Adams
2015-12-10 19:02 ` Casting as wide a net as possible John Wiegley
2015-12-10 19:07 ` Eli Zaretskii [this message]
2015-12-10 19:48 ` David Kastrup
2015-12-10 20:01 ` Eli Zaretskii
2015-12-10 20:17 ` David Kastrup
2015-12-10 20:19 ` John Wiegley
2015-12-10 20:50 ` David Kastrup
2015-12-11 7:09 ` Richard Stallman
2015-12-10 19:54 ` covici
2015-12-10 21:21 ` Marcin Borkowski
2015-12-14 13:05 ` Adrian.B.Robert
2015-12-14 16:21 ` raman
2015-12-14 18:21 ` John Wiegley
2015-12-11 7:08 ` Casting as wide a net as possible (was: First draft of the Emacs website) Richard Stallman
2015-12-11 16:14 ` Casting as wide a net as possible raman
2015-12-14 14:41 ` Filipp Gunbin
2015-12-14 15:01 ` Yuri Khan
2015-12-14 17:20 ` Filipp Gunbin
2015-12-14 17:59 ` Random832
2015-12-14 18:19 ` Yuri Khan
2015-12-15 18:12 ` Filipp Gunbin
2015-12-15 18:54 ` Random832
2015-12-15 19:03 ` Random832
[not found] <<CAJnXXogJywM4xRM9OEF1RKEwOib_G_JJvj=YThhsUwFn6gHviQ@mail.gmail.com>
[not found] ` <<fa45f69a-b8df-46f8-8fda-4735dc34e4dc@default>
[not found] ` <<m2d1uenn4h.fsf@newartisans.com>
[not found] ` <<83a8pi9l6o.fsf@gnu.org>
2015-12-10 19:15 ` Drew Adams
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=83a8pi9l6o.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=john@yates-sheets.org \
--cc=jwiegley@gmail.com \
/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).