unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: stats say SBCL is 78 875 % faster than natively compiled Elisp
Date: Fri, 17 Feb 2023 20:38:16 +0300	[thread overview]
Message-ID: <Y++7iEDT02cso5Y/@protected.localdomain> (raw)
In-Reply-To: <878rgyjgcc.fsf@dataswamp.org>

* Emanuel Berg <incal@dataswamp.org> [2023-02-16 22:47]:
> They say CL (with SBCL) is fast; and that natively compiled
> Elisp is a good step from byte-compiled Elisp, and a huge leap
> from not compiling it at all! However, compared to CL/SBCL our
> beloved Elisp/Emacs is still just a turtle on steroids ...

Emacs Lisp is not designed for mission critical applications such as
controlling rockets in the orbit. But wait, let me see:

M-x mission-control

Ah, it's there. 

Speed does not matter for purposes I need, like sales, handling
people, communicating with people.

It matters for processing of e-mails, I have already re-wrote my
program that processes mailings to thousands of people from Perl to
Common Lisp to Emacs Lisp. I prefer it in Emacs Lisp as I can
integrate it way easier with everything else. That is one thing that I
may consider maybe it could be faster, because it blocks the computer,
raises some issues, like heating.

> > SBCL does not have tabulated-list-mode and integrated editor
> > in the programming environment
> 
> Oh, we have Emacs for that! Check this out, including
> instructions how to install a bunch of stuff ...
> 
> It's SLIME ... as you know well! You are just goofing
> around. That's okay.

Is SLIME related to tabulated-list-mode?

Anyway, when I program Common Lisp, I just plain built-in lisp-mode
and it works well.

> But while I got it to work, the level of integration is still
> below what we have with Elisp. So I thought, with the native
> compile step, we could maybe ... but no. Need speed? Use CL.

I used it, I am not satisfied with it due to lack of integration.

To generate "list of things" in Common Lisp is simply difficult, it
needs some GUI and much work. Emacs has interface ready. The text
properties are great. They serve like switches for a key to provide
different functionality. I simply don't have those feautures in Common
Lisp.

There is no ready spreadsheet type of a GUI for Common Lisp where I
can make key bindings for each screen different in as simple way as
how it is in Emacs.

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/



  reply	other threads:[~2023-02-17 17:38 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14  7:56 stats say SBCL is 78 875 % faster than natively compiled Elisp Emanuel Berg
2023-02-15  5:04 ` Chen Zhaoyang
2023-02-15 11:37   ` Emanuel Berg
2023-02-15  6:59 ` Jean Louis
2023-02-16  6:04   ` Emanuel Berg
2023-02-17 17:38     ` Jean Louis [this message]
2023-02-18 19:54       ` Emanuel Berg
2023-02-18 20:15         ` Emanuel Berg
2023-02-18 20:39           ` Eli Zaretskii
2023-02-18 20:47             ` Emanuel Berg
2023-02-19  6:35               ` Eli Zaretskii
2023-02-21  7:04                 ` Native compilation by default?: Was [Re: " Madhu
2023-02-21 12:37                   ` Eli Zaretskii
2023-02-21 16:35                     ` Emanuel Berg
2023-02-21 19:57                       ` Emanuel Berg
2023-02-21 22:21                       ` Native compilation by default? (was: Re: stats say SBCL is 78 875 % faster than natively compiled Elisp) Emanuel Berg
2023-02-21 23:54                         ` Emanuel Berg
     [not found]                           ` <87h6vetquk.fsf@dataswamp.org>
2023-02-22  1:47                             ` Emanuel Berg
2023-02-23 10:46                         ` Emanuel Berg
2023-02-23 20:18                           ` Jean Louis
2023-02-26  1:05                             ` Emanuel Berg
2023-02-22 12:32                       ` Native compilation by default?: Was [Re: stats say SBCL is 78 875 % faster than natively compiled Elisp Eli Zaretskii
2023-02-26  3:08                     ` Madhu
2023-02-26  4:32                       ` Stefan Monnier via Users list for the GNU Emacs text editor
2023-02-26  5:15                         ` Emanuel Berg
2023-02-26  6:27                         ` Eli Zaretskii
2023-02-26  7:10                         ` Emanuel Berg
2023-02-26 16:14                         ` FW: [External] : " Drew Adams
2023-02-26 16:31                           ` Eli Zaretskii
2023-02-26 17:12                             ` Drew Adams
2023-02-26 17:31                               ` Eli Zaretskii
2023-02-26 18:29                                 ` Drew Adams
2023-02-26 19:04                                   ` Eli Zaretskii
2023-02-26 20:05                                     ` Emanuel Berg
2023-02-27  8:42                         ` Madhu
2023-03-03 14:55                           ` Stefan Monnier via Users list for the GNU Emacs text editor
2023-02-26  6:25                       ` Eli Zaretskii
2023-02-26 16:10                         ` [External] : " Drew Adams
2023-02-19  5:58         ` Jean Louis
2023-02-15 12:36 ` full native compile (was: Re: stats say SBCL is 78 875 % faster than natively compiled Elisp) Emanuel Berg
2023-02-15 14:05   ` Eli Zaretskii

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=Y++7iEDT02cso5Y/@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=help-gnu-emacs@gnu.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).