all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Joost Kremers <joostkremers@fastmail.fm>
To: <tomas@tuxteam.de>
Cc: emacs-devel@gnu.org
Subject: Re: Elisp threading macros
Date: Fri, 30 Aug 2024 09:30:33 +0200	[thread overview]
Message-ID: <867cbyjwme.fsf@fastmail.fm> (raw)
In-Reply-To: <Zs/8z50fI/tZYvXB@tuxteam.de> (tomas@tuxteam.de's message of "Thu, 29 Aug 2024 06:45:03 +0200")

On Thu, Aug 29 2024, tomas@tuxteam.de wrote:
> 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.

Yes, I think that's very much the point. It's more a matter of taste than
anything else. And taste for a large part depends on what one is used to.
When I first encountered Clojure, I quite disliked it. And threading
macros? You'd have to be out of your mind to write code like that...

But at some point, I decided to learn Clojure and I must admit, I really
like the language. It's different than Elisp for sure, but things that
irked me initially, I came to like eventually, because I started to see why
they were designed the way they are. (I'd actually love to do more with
Clojure, TBH...)

Still, that doesn't mean I think Elisp should become more like Clojure, of
course. (I'm actually neutral on that point.) I think the current
situation, with the seq library and thread-{first|last} available in core,
and dash.el readily available from GNU ELPA, is a good compromise. (And, to
the OP: from your perspective, probably the "best" you're gonna get. 😉)



-- 
Joost Kremers
Life has its moments



  reply	other threads:[~2024-08-30  7:30 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
2024-08-30  7:30         ` Joost Kremers [this message]
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=867cbyjwme.fsf@fastmail.fm \
    --to=joostkremers@fastmail.fm \
    --cc=emacs-devel@gnu.org \
    --cc=tomas@tuxteam.de \
    /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.