all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: emacs-devel@gnu.org
Subject: Re: Elisp threading macros
Date: Thu, 29 Aug 2024 06:45:03 +0200	[thread overview]
Message-ID: <Zs/8z50fI/tZYvXB@tuxteam.de> (raw)
In-Reply-To: <87mskws9sz.fsf@posteo.net>

[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]

On Wed, Aug 28, 2024 at 07:54:04PM +0000, Philip Kaludercic wrote:

[...]

> Generally this seems like a cultural clash between traditional Lisps and
> newer languages like Clojure that derive some inspired from Lisps, but
> have intentionally broken with the existing "Lisp tradition".
> Backporting concepts like these is certainly technically feasible, but
> it feels forced and foreign for people like me who don't work with
> Closure or related languages.

I think this is a very important point. Emacs Lisp (any language) isn't
"just" a set of rules, but a whole set of applications and a community
(or perhaps a set of interconnected communities) [0]. Each time someone
with big enthusiasm comes along and "hey, let's change everything, this
looks so much better", things tend to degrade into strange identity wars.

On the one hand, you can't just change the whole community "just like that":
people gravitate towards languages for reasons (I must admit I cringe myself
when I see those threaded macros, but then, my excursions into those newer
functional languages have never really worked). Most people are here because
they like things as they are.

On the other hand, for my taste at least, the reactions (my [1] reaction,
at that!) to those ideas feels sometimes more hostile than necessary.

I'd like (for myself!) to have better answers to that.

Cheers

[0] And a means of communication. And of identification. And...
[1] That's why I often shut up in those cases. But hostile silence
   is hostile, too. Oh, well.
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2024-08-29  4:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-28 14:08 Elisp threading macros Garklein
2024-08-28 15:51 ` Robert Pluim
2024-08-28 16:42   ` Visuwesh
2024-08-28 17:13     ` Henrik Kjerringvåg
2024-08-28 15:55 ` Eli Zaretskii
2024-08-28 18:23   ` Basil L. Contovounesios
2024-08-31 12:50   ` Augusto Stoffel
2024-08-28 18:05 ` Philip Kaludercic
2024-08-28 19:43   ` Garklein
2024-08-28 19:54     ` Philip Kaludercic
2024-08-29  4:45       ` tomas [this message]
2024-08-30  7:30         ` Joost Kremers
2024-08-29 21:19   ` Sean Whitton
2024-08-29 21:46     ` Philip Kaludercic
2024-08-28 18:29 ` Thierry Volpiatto
2024-08-28 19:35   ` Garklein
2024-08-30 12:26     ` Rudolf Adamkovič
2024-08-30 13:12       ` Robert Pluim
2024-08-30 17:15         ` [External] : " Drew Adams
2024-09-01 16:43           ` Alfred M. Szmidt
2024-09-01 21:02             ` Drew Adams
2024-08-29  0:48 ` Po Lu
2024-08-29  5:19 ` Alfred M. Szmidt
2024-08-30  0:57   ` Garklein

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=Zs/8z50fI/tZYvXB@tuxteam.de \
    --to=tomas@tuxteam.de \
    --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.