From: Jean Louis <bugs@gnu.support>
To: Hongyi Zhao <hongyi.zhao@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>,
Emanuel Berg <moasenwood@zoho.eu>
Subject: Re: For text processing, which is more powerful, emacs or perl?
Date: Sun, 20 Dec 2020 16:42:36 +0300 [thread overview]
Message-ID: <X99UzDCRa75elrMz@protected.rcdrun.com> (raw)
In-Reply-To: <CAGP6POKKXEkkx=ZJpmZhM_D2pJJQqzGHR3vj+YsTYDXaO1txyg@mail.gmail.com>
* Hongyi Zhao <hongyi.zhao@gmail.com> [2020-12-20 10:50]:
> On Sun, Dec 20, 2020 at 2:56 PM Jean Louis <bugs@gnu.support> wrote:
> >
> > * Hongyi Zhao <hongyi.zhao@gmail.com> [2020-12-20 09:19]:
> > > On Sun, Dec 20, 2020 at 1:31 PM Jean Louis <bugs@gnu.support> wrote:
> > > >
> > > > * Hongyi Zhao <hongyi.zhao@gmail.com> [2020-12-20 04:43]:
> > > > > werner@X10DAi:~$ time python3 --version >/dev/null
> > > > >
> > > > > real 0m0.086s
> > > > > user 0m0.065s
> > > > > sys 0m0.027s
> > > > > werner@X10DAi:~$ time perl --version >/dev/null
> > > > >
> > > > > real 0m0.003s
> > > > > user 0m0.003s
> > > > > sys 0m0.000s
> > > >
> > > > You did not measure the code, rather startup time to show the version.
> > >
> > > https://perlmaven.com/compare-the-speed-of-perl-and-python-regex
> >
> > I see, yes, it cannot compare well to Python. So for when speed is
> > critical it is better using Perl. Perl is/was one of my favorite
> > languages and I did everything in Perl before learning about Lisp.
> >
> > Lisp offers to me better simpler readability.
> >
> > What I am missing is simple interface and that is solved with Emacs
> > built-in features. And Emacs than provides instability so I cannot
> > really solve huge tasks with it, it crashes, has memory problems,
> > etc.
>
> Really? If so, why emacs is still the most preferred editor for top
> developers on the world?
What I do is not really editing, it is harvesting data and entering
into database without pause. So it blocks Emacs while doing it.
Most of times Emacs is handling what I want.
But I will most probably delegate some tasks to Erlang language or
Common Lisp.
next prev parent reply other threads:[~2020-12-20 13:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 7:43 For text processing, which is more powerful, emacs or perl? Hongyi Zhao
2020-12-19 9:00 ` Jean Louis
2020-12-19 12:17 ` Hongyi Zhao
2020-12-19 12:25 ` Jean Louis
2020-12-20 0:04 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-20 1:42 ` Hongyi Zhao
2020-12-20 3:07 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-20 5:31 ` Jean Louis
2020-12-20 6:18 ` Hongyi Zhao
2020-12-20 6:52 ` Jean Louis
2020-12-20 7:49 ` Hongyi Zhao
2020-12-20 13:42 ` Jean Louis [this message]
2020-12-20 3:03 ` Hongyi Zhao
2020-12-20 3:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-08 16:42 ` Marcin Borkowski
2020-12-19 14:36 ` Harald Jörg
2020-12-20 4:38 ` Jean Louis
2020-12-19 16:01 ` Stefan Monnier
2020-12-20 5:23 ` Jean Louis
2020-12-20 6:17 ` Hongyi Zhao
2020-12-20 6:25 ` Jean Louis
2020-12-20 13:58 ` Stefan Monnier
2020-12-20 14:47 ` tomas
2020-12-20 9:01 ` tomas
2021-10-08 16:52 ` Marcin Borkowski
2021-10-09 1:42 ` Hongyi Zhao
2021-10-10 14:26 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=X99UzDCRa75elrMz@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=hongyi.zhao@gmail.com \
--cc=moasenwood@zoho.eu \
/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).