unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: [External] : A peek to the other side
Date: Sat, 26 Feb 2022 04:36:23 +0100	[thread overview]
Message-ID: <871qzq8fk8.fsf@zoho.eu> (raw)
In-Reply-To: SJ0PR10MB5488A4B46C87A07BAE1C7351F33B9@SJ0PR10MB5488.namprd10.prod.outlook.com

Drew Adams wrote:

> The tendency to think in strong black-&-white,
> internal/external, baked/fluid, closed/open terms comes also
> (I think) from the fact that developers come to Emacs and
> Elisp from working with other, more static/structured
> languages and environments - worlds where there really can
> be a strong use and need for an inside/outside separation
> and protecting coders from themselves and code from itself
> (beyond purposes of abstraction).

If nothing in terms of technology separates them, no need to
invent something artificial that pretends to do that, if
that's what happens.

If an alien race of super-hackers conquered Earth, beings
that were totally ignorant about humans but could immediately
and fully understand any piece of code they were looking at
... would they see the same thing two times, or different
things one time each?

Interestingly we, who are still humans most of us, should use
the same method ...

-- 
underground experts united
https://dataswamp.org/~incal




  parent reply	other threads:[~2022-02-26  3:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22  7:11 A peek to the other side emacsq via Users list for the GNU Emacs text editor
2022-02-22 16:11 ` [External] : " Drew Adams
2022-02-22 16:46   ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-02-22 18:25     ` Drew Adams
2022-02-22 18:43       ` Eli Zaretskii
2022-02-22 19:38         ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-02-26  3:45       ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-23 12:24   ` Arthur Miller
2022-02-23 13:50     ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-02-26  3:36   ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2022-02-22 18:21 ` Samuel Banya
2022-02-22 19:17   ` Philip Kaludercic
2022-02-22 21:31     ` Samuel Banya
2022-02-23 12:05 ` Arthur Miller

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=871qzq8fk8.fsf@zoho.eu \
    --to=help-gnu-emacs@gnu.org \
    --cc=moasenwood@zoho.eu \
    /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).