Re: Threads across programming languages

On 4/30/2024 12:37 AM, Bonita Montero wrote:

Am 30.04.2024 um 08:42 schrieb Lawrence D'Oliveiro:

On Tue, 30 Apr 2024 07:59:06 +0200, Bonita Montero wrote:
>

Am 30.04.2024 um 06:09 schrieb Lawrence D'Oliveiro:

>
On Tue, 30 Apr 2024 05:58:31 +0200, Bonita Montero wrote:
>

Having a single thread and using state machines is more effortz.

>
It would indeed. That’s why coroutines (async/await) are so handy.

>
Using a thread is even more handy.

>
Do you know what a “heisenbug” is?

 This has nothing to do with a heisenbug. Threads are slightly less
performance than managing state with a coroutine,

Huh? Threads allow one to take advantage of the processing power of a multi-core/socket system. We can multiplex coroutines on a single thread, okay fine, ugg... This is not going to use the full spectrum of a system wrt multiple processing units. We can decide to use at least as many threads as there are cores. This can get the full power of said system. Sometimes using number_of_cores * 2 threads might be in order.

but they're more
convenient to develop. In Python the difference wouldn't count.