> My possibly Luddite opinion is that using the most amazing and surprising new C++ features is not the best way to build code consumed by others. It's ok if y

> My possibly Luddite opinion is that using the most amazing and surprising new C++ features is not the best way to build code consumed by others. It's ok if you opt to not jump onto the latest and greatest, specially at the interface level. What is counterproductive is to not learn new features, and know when and when not to use them. It makes absolutely no sense to stay stuck in C++11 when there's a heap of basic features that were since made available throughout the last decade. It's even more critical the fact that the C++ standardization effort placed a great deal of effort on vocabulary types, which by its own definition mean types excpliticly designed to be used in interfaces. It's perfectly ok to make a call to not use exceptions, template metaprogramming, multi threaded support, etc. What's counterproductive is staying stuck way back in 2011 because you do not know what's out there.