From: "Abraham S.A.H." via "Emacs development discussions." <emacs-devel@gnu.org>
To: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: 10 problems with Elisp, part 10
Date: Tue, 6 Aug 2024 19:38:28 +0200 (CEST) [thread overview]
Message-ID: <O3cegte--B-9@tuta.io> (raw)
> Yes, Python is incomparable to Emacs Lisp and would probably
win quite even against the collective Lisp world, I'm afraid.
Wins only in being popular. It can win against most languages in that regard and I doubt if it's only for technical reasons.
> if we care about Lisp we should
do what we can to make Elisp more competitive altho we should
focus on getting better, and not compare us to other languages
as we are way too far behind in many areas, I'm afraid.
Sure. But should we consider Python as a technically better language?
Of course it has lessons to be learnt and advantages to be studied and adopted. But should one try to make Elisp more like JS or PHP or Python just because they have more programmers? Isn't it because of some other industrial causes that they are popular?
And are you sure that what you mentioned in number 10 is Emacs' weakness and not its advntage?
--
Best Regards,
next reply other threads:[~2024-08-06 17:38 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 17:38 Abraham S.A.H. via Emacs development discussions. [this message]
2024-08-07 7:44 ` 10 problems with Elisp, part 10 Emanuel Berg
2024-08-07 11:30 ` Christopher Dimech
2024-10-23 19:34 ` Lisp sooo much better than Python - " Jean Louis
-- strict thread matches above, loose matches on Subject: below --
2024-08-09 7:21 Johan Myréen
2024-08-07 18:57 Abraham S.A.H. via Emacs development discussions.
2024-08-07 20:46 ` Sebastián Monía
2024-08-08 4:58 ` Eli Zaretskii
2024-08-08 5:40 ` Christopher Dimech
2024-08-08 6:00 ` Dr. Arne Babenhauserheide via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2024-08-09 7:08 ` Emanuel Berg
2024-08-09 8:21 ` Dr. Arne Babenhauserheide
2024-08-09 8:36 ` Emanuel Berg
2024-08-09 10:46 ` Eli Zaretskii
2024-08-09 22:27 ` Emanuel Berg
2024-08-09 13:47 ` Eduardo Ochs
2024-08-09 14:03 ` Emanuel Berg
2024-08-09 22:47 ` Bob Rogers
2024-08-09 23:21 ` Emanuel Berg
2024-08-10 5:56 ` Eli Zaretskii
2024-08-11 2:12 ` Richard Stallman
2024-10-23 20:11 ` Jean Louis
2024-10-23 20:06 ` Jean Louis
2024-10-29 13:42 ` Abraham S.A.H. via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2024-08-04 22:27 Emacs website, Lisp, and other Jeremy Bryant
2024-08-04 22:55 ` Emanuel Berg
2024-08-05 9:23 ` Christopher Dimech
2024-08-05 12:28 ` Eli Zaretskii
2024-08-05 16:27 ` 10 problems with Elisp, part 10 (was: Re: Emacs website, Lisp, and other) Emanuel Berg
2024-08-05 16:38 ` Eli Zaretskii
2024-08-05 17:03 ` Emanuel Berg
2024-08-05 18:32 ` 10 problems with Elisp, part 10 Dr. Arne Babenhauserheide
2024-08-05 20:20 ` Emanuel Berg
2024-08-06 7:14 ` Dr. Arne Babenhauserheide
2024-08-06 11:54 ` Eli Zaretskii
2024-08-08 2:01 ` Richard Stallman
2024-08-09 22:39 ` Emanuel Berg
2024-08-13 1:28 ` Richard Stallman
2024-08-09 22:46 ` Emanuel Berg
2024-08-10 5:41 ` Emanuel Berg
2024-08-10 6:09 ` Eli Zaretskii
2024-08-13 1:28 ` Richard Stallman
2024-08-05 18:58 ` 10 problems with Elisp, part 10 (was: Re: Emacs website, Lisp, and other) Christopher Dimech
2024-08-05 19:30 ` 10 problems with Elisp, part 10 Dr. Arne Babenhauserheide
2024-08-05 20:02 ` Christopher Dimech
2024-08-08 2:01 ` Richard Stallman
2024-08-06 2:28 ` Eli Zaretskii
2024-10-23 19:25 ` 10 problems with Elisp, part 10 (was: Re: Emacs website, Lisp, and other) Jean Louis
2024-10-23 21:13 ` 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
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=O3cegte--B-9@tuta.io \
--to=emacs-devel@gnu.org \
--cc=arash.sah@tuta.io \
/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.