First of all, agree with your decision to use C++17. Great idea! However, in our case (like with many C++ code bases) the code was almost 20 years old. Even wi

First of all, agree with your decision to use C++17. Great idea! However, in our case (like with many C++ code bases) the code was almost 20 years old. Even with the Herculean efforts made by the teams to keep the code base up to date and refactored, you run into issues of backwards compatibility with older libraries. C++17 is definitely the go to for new projects! However, I've never personally worked on a pure green field project written in C++ that didn't have to latch onto some older libraries that require older C++ std versions.