From: Jean Louis <bugs@gnu.support>
To: emacs-tangents@gnu.org
Cc: Emanuel Berg <incal@dataswamp.org>
Subject: Re: 10 problems with Elisp, part 10 (was: Re: Emacs website, Lisp, and other)
Date: Wed, 23 Oct 2024 22:25:16 +0300 [thread overview]
Message-ID: <ZxlNnJyscy_yALFz@lco2> (raw)
In-Reply-To: <87frrjoryg.fsf_-_@dataswamp.org>
* Emanuel Berg <incal@dataswamp.org> [2024-08-05 19:31]:
> Eli Zaretskii wrote:
>
> > Please, everybody, take the Lisp vs Python argument off this
> > list, it is off-topic here. If you must discuss this, please
> > use the emacs-tangents@gnu.org mailing list instead.
>
> Sure, but we are allowed to discuss how to make Elisp better?
>
> Since Python has had enormous success, and Lisp hasn't - or if
> it had, it lost it - it might be a good ide to analyze what
> they (Python) did good.
Do you mean making Elisp better in the eyes of the world, or technically for Elisp users?
There are obviously many Elisp users, worth enough for developing it
technically, improving it, that is fine and good. And developers are
doing it. We are here in society of Elisp users.
For the eyes of the world, does it matter? I do not see how it does
matter. Last time I checked, there must be millions of Emacs
users. Not all of them are loud and talking. I just guess that
majority does not even know about Elisp. But there is large number of
Emacs users, as there is large number of GNU/Linux users, and growing.
They may open editor and write something. They may not know about
Elisp, though they soon find out, so it is surely growing. Watching
our mailing lists I can see new users coming.
Comparisons like Python vs Elisp are useless as it is just interesting
for discussion and some language wars in old style.
What is useful is practical program, software, which is made and
provides final benefits.
A single program, no matter the language, can provide huge success.
For more technical insight into the war general Lisp vs Python:
http://www.norvig.com/python-lisp.html
> Apply on data in data structures, not on data as it appears in
> Emacs buffers.) But how ever well one does, it is gonna be _a
> lot_ of of moving point around in Emacs Lisp, so don't worry :)
Statements were exaggerated. You have various data structures, and if
you need to operate on buffer, operate. Personally I operate on
hashes, and lists, and vectors, etc. Not on buffers. I cannot find
your statement universal.
> Example of problem from my favorite part of Emacs, ispell.el:
>
> (defun ispell-mime-multipartp (&optional limit)
> "Return multipart message start boundary or nil if none."
> ;; caller must ensure `case-fold-search' is set to t
> (and
> (re-search-forward
> "Content-Type: *multipart/\\([^ \t\n]*;[ \t]*[\n]?[ \t]*\\)+boundary="
> limit t)
> (let (boundary)
> (if (looking-at "\"")
> (let (start)
> (forward-char)
> (setq start (point))
> (while (not (looking-at "\""))
> (forward-char 1))
> (setq boundary (buffer-substring-no-properties start (point))))
> (let ((start (point)))
> (while (looking-at "[-0-9a-zA-Z'()+_,./:=?]")
> (forward-char))
> (setq boundary (buffer-substring-no-properties start (point)))))
> (if (< (length boundary) 1)
> (setq boundary nil)
> (concat "--" boundary)))))
>
> Moving point around, looking, searching, seeing or not seeing.
> This is boring and error prone to write, and error prone to
> take over from someone else, or return to after x years.
Come on. All programming is about looking, searching, and of course it
can be boring and error prone, I remember machine language, of course
it is error prone, there is no programming language not error prone.
> You don't think in terms of the problem, or the solution for
> that matter, you are just somewhere in the buffer and
> according the the map you are completely lost!
That is why some developers are lost, some are okay with it.
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
✡️🛡️ Proudly standing with Israel, a nation rooted in history and culture. Let's condemn hatred and promote understanding.
In support of Richard M. Stallman
https://stallmansupport.org/
---
via emacs-tangents mailing list (https://lists.gnu.org/mailman/listinfo/emacs-tangents)
next prev parent reply other threads:[~2024-10-23 19:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87sevj9b50.fsf@jeremybryant.net>
[not found] ` <871q33rj7v.fsf@dataswamp.org>
2024-08-05 20:03 ` Emacs website, Lisp, and other Alan Mackenzie
2024-08-05 21:07 ` Christopher Dimech via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2024-08-06 7:42 ` Jean Louis
2024-08-06 11:14 ` Immanuel Litzroth
[not found] ` <trinity-dae5eb6f-9f3b-451e-ac64-5d82d5ea1bef-1722849793865@3c-app-mailcom-bs04>
[not found] ` <86ed73qhly.fsf@gnu.org>
[not found] ` <87frrjoryg.fsf_-_@dataswamp.org>
2024-10-23 19:25 ` Jean Louis [this message]
2024-10-23 21:13 ` 10 problems with Elisp, part 10 (was: Re: Emacs website, Lisp, and other) Emanuel Berg
2024-10-23 21:36 ` Jean Louis
2024-10-25 6:44 ` Emanuel Berg
2024-10-28 3:27 ` 10 problems with Elisp, part 10 Joel Reicher
2024-10-24 6:48 ` Dr. Arne Babenhauserheide via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
[not found] ` <86h6bzqj2v.fsf@gnu.org>
[not found] ` <87ed718o45.fsf@jeremybryant.net>
[not found] ` <trinity-095d4d25-5510-4167-81eb-124105b9eaf2-1722973850111@3c-app-mailcom-bs08>
2024-10-23 19:41 ` Emacs website, Lisp, and other Jean Louis
2024-10-24 6:39 ` Dr. Arne Babenhauserheide via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
[not found] ` <BLAPR10MB5219692C7A9F536BCA442ABDF3BF2@BLAPR10MB5219.namprd10.prod.outlook.com>
[not found] ` <87wmktb8w7.fsf@web.de>
[not found] ` <DS7PR10MB52323E8786643BA9ADC6E45DF3BF2@DS7PR10MB5232.namprd10.prod.outlook.com>
2024-10-23 19:45 ` [External] : " Jean Louis
2024-10-23 20:25 ` Drew Adams via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2024-10-23 20:50 ` Jean Louis
2024-10-23 21:21 ` Drew Adams via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2024-10-23 21:37 ` Jean Louis
[not found] ` <87le186g3f.fsf@dataswamp.org>
[not found] ` <m3v802l9vn.fsf@leonis4.robolove.meer.net>
[not found] ` <87ed6qbah6.fsf@dataswamp.org>
[not found] ` <m3o75ukuvn.fsf@leonis4.robolove.meer.net>
[not found] ` <87cyma5crl.fsf@dataswamp.org>
2024-10-23 19:48 ` Jean Louis
[not found] ` <87bk1ub98z.fsf@dataswamp.org>
2024-10-23 19:52 ` Jean Louis
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=ZxlNnJyscy_yALFz@lco2 \
--to=bugs@gnu.support \
--cc=emacs-tangents@gnu.org \
--cc=incal@dataswamp.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.
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).