feelamee 3 days ago

Ok. Please, just use your current C++ standard. But we will go to use the new one with all features we want to use.

1
blub 2 days ago

Who’s “we”? The C++ developers that like the “Safe C++” proposal which is tacking Rust on top of C++ are a tiny minority.

It seems very fair to tell them to just use Rust and leave C++ alone.

pjmlp 2 days ago

Indeed, that is exactly what many FAANG companies are doing, have you noticed the slow down in velocity in major compilers regarding ISO C++ compliance?

bobnamob 2 days ago

See Apple’s slowdown on clang development and subsequent advances in Swift<->C++ interop (even going as far as merging Swift code into FoundationDB)

And ofc Google’s investment in Carbon

pjmlp 2 days ago

Or MSVC slow pace with C++23, after being the first to reach full C++20 support.

Everyone else outside the big three, is somewhere between C++14 and C++17.

blub 2 days ago

Nope, still using C++17 and not bothered by any slowdown. C++ has been moving too fast lately.

pjmlp 2 days ago

It is currently an open debate what will be the very last ISO version the world will care about, C++17 might be the one, or C++26, bets are open.

feelamee 2 days ago

obviosly.. we is

> Relatively modern, capable tech corporations that understand that their code is an asset. (This isn’t strictly big tech. Any sane greenfield C++ startup will also fall into this category.)

and @bagxrvxpepzn is ofc

> Every ancient corporation where people are still fighting over how to indent their code, and some young engineer is begging management to allow him to set up a linter.

:)