As long as old code continues to compile and run correctly on new compiler/language versions, I don't care what the committee does. From my point of view they should first and formost decelerate, so that there is at least enough time for compiler writers to keep up and collect enough experience between the standards. Cross-compiler compatibility has become an adventure since C++11. I only use a very conservative subset of the language to maintain compatibility.
Comments
As long as old code continues to compile and run correctly on new compiler/language versions, I don't care what the committee does. From my point of view they should first and formost decelerate, so that there is at least enough time for compiler writers to keep up and collect enough experience between the standards. Cross-compiler compatibility has become an adventure since C++11. I only use a very conservative subset of the language to maintain compatibility.
This is what I do in my own projects, but I don't have that option at work.