Deutsch   English   Français   Italiano  
<cone.1735491465.188366.209723.1000@ripper.email-scan.com>

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

Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Sam <sam@email-scan.com>
Newsgroups: comp.lang.c++
Subject: Re: We have a new standard!
Date: Sun, 29 Dec 2024 11:57:45 -0500
Organization: A noiseless patient Spider
Lines: 26
Message-ID: <cone.1735491465.188366.209723.1000@ripper.email-scan.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>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; delsp=yes; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 29 Dec 2024 17:57:48 +0100 (CET)
Injection-Info: dont-email.me; posting-host="4e59d07fcb0848232eb80bfdf80b1c77";
	logging-data="1148075"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18LPkuKswdDc7CZk21TtSKa"
Cancel-Lock: sha1:ME24BN0T0sbUtlz0covo81wxMc4=
Content-Disposition: inline
X-Shameless-Plug: https://github.com/svarshavchik
X-Mailer: https://www.courier-mta.org/cone/
Bytes: 2392

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.