Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Paul Rubin <no.email@nospam.invalid>
Newsgroups: comp.lang.python
Subject: Re: Does Python Need Virtual Threads? (Posting On Python-List Prohibited)
Date: Sat, 14 Jun 2025 04:29:07 -0700
Organization: A noiseless patient Spider
Lines: 7
Message-ID: <8734c236kc.fsf@nightsong.com>
References: <102isqb$3v5j0$2@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Date: Sat, 14 Jun 2025 13:29:08 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="18e41a7ce49e105c09814805ef7eb15b";
	logging-data="180017"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+KdI0OHCARZffMFGSggCHI"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
Cancel-Lock: sha1:fyhaSUKy/kXFVd3FjGHs8oYGrrQ=
	sha1:Sj4clKxxiinTpe1vLdKGDkjjzrI=

Lawrence D'Oliveiro <ldo@nz.invalid> writes:
> Looking at that Java spec, a “virtual thread” is just another name for 
> “stackful coroutine”. Because that’s what you get when you take away 
> implicit thread preemption and substitute explicit preemption instead.

Try using Erlang a little,  It has preemptive lightweight processes and
it is great.  Much better than async/await imho.