Deutsch   English   Français   Italiano  
<20241229195025.00007ae3@yahoo.com>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Michael S <already5chosen@yahoo.com>
Newsgroups: comp.lang.c++
Subject: Re: We have a new standard!
Date: Sun, 29 Dec 2024 19:50:25 +0200
Organization: A noiseless patient Spider
Lines: 46
Message-ID: <20241229195025.00007ae3@yahoo.com>
References: <cone.1735354270.316807.177566.1000@ripper.email-scan.com>
	<vkojb7$96o6$1@dont-email.me>
	<vkpelh$c5a1$1@dont-email.me>
	<vkr5ka$sp2b$1@dont-email.me>
	<cone.1735480216.541864.207895.1000@ripper.email-scan.com>
	<vkrsit$12eo6$1@dont-email.me>
	<cone.1735491465.188366.209723.1000@ripper.email-scan.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 29 Dec 2024 18:50:32 +0100 (CET)
Injection-Info: dont-email.me; posting-host="b8b40675b9c53a9094c6c8a24128d9d0";
	logging-data="1011330"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX192/9DzXo3Rbn96arJneCxl12pbC6p4CLk="
Cancel-Lock: sha1:6y9cPOZvtbjkAzmzxnPVsWfwGFU=
X-Newsreader: Claws Mail 4.1.1 (GTK 3.24.34; x86_64-w64-mingw32)
Bytes: 3138

On Sun, 29 Dec 2024 11:57:45 -0500
Sam <sam@email-scan.com> wrote:

> Muttley@dastardlyhq.com writes:
> 
> > On Sun, 29 Dec 2024 08:50:16 -0500
> > Sam <sam@email-scan.com> gabbled:  
> >> But C++20 jumped the shark, when the standardization process was
> >> hijacked by Microsoft in order to cram coroutines into the
> >> language, which noone wanted, cared, or asked for, simply because
> >> the standard threading model in Windows blows chunks, performance
> >> wise, and Microsoft desperately needed a multithreading model that
> >> did not suck.  
> >
> > I looked at co-routines and wondered wtf the author(s) was smoking.
> > How its supposed to be simpler than simply using a local state
> > machine beats the fsckout of me.  
> 
> Everything will make sense to you when you look at the co-routines  
> proposal, and note its authorship:
> 
> https://isocpp.org/files/papers/N4402.pdf
> 
> Visual C++ does not have an impressive track record of zippy
> adoptions of new C++ language feature. Most of the time it gets
> beaten to the punch by gcc. Weirdly, it was the first out of the gate
> with co-routines.
> 
> As I said: std::thread blows chunks on Windows. This was Microsoft's  
> solution.
>

That makes no sense.
If Microsoft was so concerned about lack of competitiveness of
std::thread under Windows then it would campaign for addition to the
standard of non-joinable threads (a.k.a. thread pools, a.k.a. work
items) rather than of coroutines. May be, also for addition of IO
completion ports, although those are much harder to standardize in
OS-independent manner.
The third possibility would be addition of stackful co-routines (a.k.a.
fibers, a.k.a. cooperatively scheduled threads).
Stackless coroutines of C++ serve non-trivially different purposes than
all things mentioned above and unlikely to replace threads except in
*very* unusual circumstances.