unofficial mirror of emacs-tangents@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Emanuel Berg <incal@dataswamp.org>
Cc: emacs-tangents@gnu.org
Subject: Re: 10 problems with Elisp, part 10 (was: Re: Emacs website, Lisp, and other)
Date: Thu, 24 Oct 2024 00:36:14 +0300	[thread overview]
Message-ID: <ZxlsTjffv_gjYJHv@lco2> (raw)
In-Reply-To: <87h692ed5s.fsf@dataswamp.org>

* Emanuel Berg <incal@dataswamp.org> [2024-10-24 00:13]:
> Jean Louis wrote:
> 
> >> 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?
> 
> How nice to hear from you, thanks for helping me out that
> other time, so okay, this old and boring discussion tho - I'm
> just gonna answer this one message - okay - ... - really,
> ONE message, I saying.
> 
> First, what I mean "better": as a programming language,
> as technology.

I am here only to poke on you ;-)

But I can't replace Emacs Lisp with something else. I have got
interface and it is sufficient, I need not think of plethora of
elements. We manage employees, documents, accounting, reports of all
kinds, I mean it is huge. I have switched from Perl to Emacs.

** Statistics 

╔════════════════════════╦════════╦══════════════════════════════╦═══════╗
║ Total number of people ║ 242546 ║ Total Hyperdocuments         ║ 62993 ║
╠════════════════════════╬════════╬══════════════════════════════╬═══════╣
║ People in last week    ║ 108    ║ Hyperdocuments in last week  ║ 216   ║
╠════════════════════════╬════════╬══════════════════════════════╬═══════╣
║ People in last month   ║ 261    ║ Hyperdocuments in last month ║ 841   ║
╚════════════════════════╩════════╩══════════════════════════════╩═══════╝

All that above is managed through Emacs interface.

So if Python is better, it is for me personal issue, not technical
issue. I have got no oversight and capacity to measure what is better.


-- 
Jean


---
via emacs-tangents mailing list (https://lists.gnu.org/mailman/listinfo/emacs-tangents)

  reply	other threads:[~2024-10-23 21:36 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         ` 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 [this message]
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=ZxlsTjffv_gjYJHv@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).