Warning: mysqli::__construct(): (HY000/1203): User howardkn already has more than 'max_user_connections' active connections in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\includes\artfuncs.php on line 21
Failed to connect to MySQL: (1203) User howardkn already has more than 'max_user_connections' active connections
Warning: mysqli::query(): Couldn't fetch mysqli in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\index.php on line 66
Article <v0pqsr$28g0v$3@dont-email.me>
Deutsch   English   Français   Italiano  
<v0pqsr$28g0v$3@dont-email.me>

View for Bookmarking (what is this?)
Look up another Usenet article 
Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.lang.c++,comp.lang.c
Subject: Re: Threads across programming languages
Date: Tue, 30 Apr 2024 04:09:00 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 18
Message-ID: <v0pqsr$28g0v$3@dont-email.me>
References: <GIL-20240429161553@ram.dialup.fu-berlin.de>
	<v0oh9f$1rdff$1@raubtier-asyl.eternal-september.org>
	<v0p02j$1ur12$5@dont-email.me>
	<v0pq95$28cml$1@raubtier-asyl.eternal-september.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 30 Apr 2024 06:09:00 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="7b9c5c061751fa9a194e47f34ce1cb82";
	logging-data="2375711"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+vsy0Jldiy6hjq0XRrZpVM"
User-Agent: Pan/0.155 (Kherson; fc5a80b8)
Cancel-Lock: sha1:f0BagL4LupCXvOAFdlt5I7ztyos=
Bytes: 1874

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

> Am 29.04.2024 um 22:31 schrieb Lawrence D'Oliveiro:
>
>> On Mon, 29 Apr 2024 18:18:57 +0200, Bonita Montero wrote:
>> 
>>> But you need multithreading to have maximum throughput since you often
>>> process the data while other data is available.
>> 
>> In a lot of applications, the bottleneck is the network I/O, or a GUI
>> waiting for the next user event, that kind of thing. In this situation,
>> multithreading is more trouble than it’s worth. This is why coroutines
>> (in the form of async/await) have made a comeback over the last decade
>> or so.
> 
> Having a single thread and using state machines is more effortz.

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