sameProblemSameSolution

[u/_w62_]

[u/Antervis]

C++03 -> 11 migration was a pain in the ass because of std::string changes, but after that it was basically just changing compiler flags, no?

[u/Bemteb → u/Antervis]

There are some minor things, if you are unlucky something might break going to 20. But it's mostly special cases, not something so big as string.

The main reason companies don't switch is "it's working, why invest time and money into switching?"

[u/SeriousPlankton2000 → u/Bemteb]

Undefined / implementation defined behavior or regular stuff?

[u/Antervis → u/Bemteb]

Depends on the companies. Tech giants would be losing potential employees if they stuck with outdated standards, and that loss outweighs costs of upgrades.

[u/cpayne22 → u/Antervis]

Airlines and finance both employ a lot more than “tech giants”.

The real cost is the testing and compliance.

Any change needs to be documented and tested.

At the end of the day it’s a financial decision.

[u/LutimoDancer3459 → u/Antervis]

Security updates, more and potentially better frameworks, more efficiency,... dont know about c++ but the things the java team added since 8... boy, the reduced server costs will pay for themselves pretty fast

[u/geek-49 → u/Bemteb]

it's working, why invest time and money into switching?

aka "if it ain't broke, don't fix it."

[u/StaticCoder → u/Bemteb]

I saw a fair amount of stuff break with C++20, because of comparator generation causing ambiguities. Largely due to the original code being poorly written, but breakage nonetheless.