Path: ...!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Muttley@dastardlyhq.com Newsgroups: comp.lang.c++ Subject: Re: We have a new standard! Date: Sun, 29 Dec 2024 16:15:25 -0000 (UTC) Organization: A noiseless patient Spider Lines: 30 Message-ID: References: Content-Type: text/plain; format=flowed; delsp=yes; charset="UTF-8" Injection-Date: Sun, 29 Dec 2024 17:15:25 +0100 (CET) Injection-Info: dont-email.me; posting-host="50adee42a6747628225b2a3bdc1601fe"; logging-data="1129222"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/0iHb6T2DVLpOEd22+qNnU" Cancel-Lock: sha1:do6OmkXfylXy5S0trJ5Ui/Jy+FQ= Bytes: 2328 On Sun, 29 Dec 2024 08:50:16 -0500 Sam gabbled: >Muttley@dastardlyhq.com writes: > >> On Sat, 28 Dec 2024 13:05:37 -0500 >> Phillip gabbled: >>> I'm still on C++98 and C++03. Everything beyond that is just bloat to me. >;-) >> >> I would say that C++ 11 did improve things particularly wrt the STL and >> possibly 2014 was the high point. Beyond that its been as you say pointless >> bloat that achieves nothing. > >I would say that C++17 was also an incremental improvement. I'll give you shared_mutex that came with 17, but really that should have been in from 2011 when threading was added. Not having 3 level thread locking from the get go was ridiculous. But the rest of 17 ... meh. >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 fsck out of me.