all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Arthur Miller <arthur.miller@live.com>
Cc: emacs-devel@gnu.org
Subject: Re: Info: No GIL Multithreading strat for Python
Date: Sun, 03 Mar 2024 17:56:17 +0200	[thread overview]
Message-ID: <86bk7vnwbi.fsf@gnu.org> (raw)
In-Reply-To: <DU2PR02MB101096A09AF0472764A7AB3DB965C2@DU2PR02MB10109.eurprd02.prod.outlook.com> (message from Arthur Miller on Sun, 03 Mar 2024 12:50:18 +0100)

> From: Arthur Miller <arthur.miller@live.com>
> Date: Sun, 03 Mar 2024 12:50:18 +0100
> 
> 
> I just stumbled over an intersting presentation of a multithreading experiment
> for a "no-gil" Python, with relatively well-explained strategy they use,
> problems they face and what it offers:
> 
> https://www.youtube.com/watch?v=rImAmkS2ySE&t=2s
> 
> The presentation is about ~ ½ year old, I have no idea what is the status and
> how well it works. But some of what they discuss is perhaps of the interest for
> emacs devs.

Python is a programming language, where the programmers are
responsible for what the parallel programs they write do and how do
they cope with the various dangers of concurrency.  If the program
crashes, the programmer has only him/herself to blame.

By contrast, Emacs is a program that lets users process text in
various scenarios, where users expect Emacs to react gracefully to
errors.  Emacs the program has a very large global state that doesn't
work well with any concurrency, and which any programmer will keep as
far from as possible.  If Emacs crashes, users blame Emacs, not the
Lisp they wrote.

So there's a large difference, and therefore not every technique used
by a programming language can be used by Emacs to achieve similar
goals.



  reply	other threads:[~2024-03-03 15:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-03 11:50 Info: No GIL Multithreading strat for Python Arthur Miller
2024-03-03 15:56 ` Eli Zaretskii [this message]
2024-03-03 19:01   ` Arthur Miller
2024-03-03 19:32     ` Eli Zaretskii
2024-03-04 12:19       ` Arthur Miller
2024-03-04 12:44         ` Eli Zaretskii
2024-03-04 15:55           ` Arthur Miller
2024-03-04 16:30           ` Konstantin Kharlamov
2024-03-04 16:50             ` Eli Zaretskii
2024-03-05  0:44               ` chad
2024-03-05  0:44               ` chad

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=86bk7vnwbi.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=arthur.miller@live.com \
    --cc=emacs-devel@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.
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.