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
Date: Wed, 23 Oct 2024 23:11:33 +0300 [thread overview]
Message-ID: <ZxlYdQg-XFAxiriO@lco2> (raw)
In-Reply-To: <877ccq5g2u.fsf@dataswamp.org>
* Emanuel Berg <incal@dataswamp.org> [2024-08-09 10:20]:
> Abraham S.A.H." via "Emacs development discussions. wrote:
>
> >> It doesn't take much experience to do cool things fast in
> >> Python, it is a fact.
> >
> > I agree to disagree, Emanuel! Sorry, but I do not think
> > "Python is a generally better programming language".
>
> Devel time faster than in Lisp, is what I'm saying.
I believe that the speed of development is influenced by how the
programmer has structured the foundational components.
I believe Lisp-like languages are ideal for this purpose. Unlike many
other languages, which can make speeding up development a challenge,
Lisp-like languages make the process much easier and more
straightforward.
I am sorry that you haven't arrived at that understanding yet, but
it's great that you grasped it in another language.
What works, works.
I would use software in any language if it gives me product or service
I need.
> Maybe one could have a Lisp that also was as fast or almost as
> fast, if one focused on that aspect.
I gave you references, Lisp is so much faster than your praised babies.
---
via emacs-tangents mailing list (https://lists.gnu.org/mailman/listinfo/emacs-tangents)
next prev parent reply other threads:[~2024-10-23 20:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <O3hwhNN--7-9@tuta.io>
2024-08-08 6:00 ` 10 problems with Elisp, part 10 Dr. Arne Babenhauserheide via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
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
[not found] ` <877ccq5g2u.fsf@dataswamp.org>
2024-10-23 20:11 ` Jean Louis [this message]
[not found] <87sevj9b50.fsf@jeremybryant.net>
[not found] ` <871q33rj7v.fsf@dataswamp.org>
[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 ` 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
2024-08-09 7:21 Johan Myréen
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=ZxlYdQg-XFAxiriO@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).