I know about Scott Meyers publications (https://en.wikipedia.org/wiki/Scott_Meyers#Publications). I've read all over the internet these books are a must read.<p>Is this still true for somebody who wants to learn C++ in depth in 2021? I have plenty of experience using C and C++ over the years, nevertheless my coding in C++ still feels like doing C with classes and some STL containers like 2005. I want to progress from this state.<p>Are the books of Scott Meyers still the ones I should read now? If not, what are the new 'standard' books I should read?
In my humble opinion, any C++ developer wants to call him or her self a professional must read his books...all of them!<p>So, to recap, here are the names of C++ specialists you need to read their books and / or articles they publish:<p><pre><code> * Bjarne Stroustrup of course
* Andrei Alexandrescu
* Scott Meyers
* Herb Sutter
* Jason Turner (His YouTube channel is a must; too many goodies in it!)
* Nicolai Josuttis
* John Lakos
</code></pre>
If you just want to revise your C++ knowledge and bring it up to date, just read the following repo and you are good to go <a href="https://github.com/AnthonyCalandra/modern-cpp-features" rel="nofollow">https://github.com/AnthonyCalandra/modern-cpp-features</a>
> "... my coding in C++ still feels like doing C with classes and some STL containers like 2005. I want to progress from this state. ..."<p>What's wrong with these?:<p>- C++: The Core Language by Gregory Satir and Doug Brown<p>- <a href="https://github.com/QuantumLeaps/OOP-in-C" rel="nofollow">https://github.com/QuantumLeaps/OOP-in-C</a><p>- C++ Concurrency in Action<p>- C++ Templates the Complete Guide 2e<p>The first is particularly geared towards C programmers, and I prefer the second one to "Inside the C++ Object Model". (There's also another popular book by a German author who covers OOP in C.)<p>For the time being, I will be an "opportunist" who is waiting for the right time to switch to another language - Rust:<p>"To me using C++ means you are ready to give up a lot of time and energy in order to gain a complete control over certain aspects of your program. I was very much into that at the start of my career and gradually started drifting away to more immediate productivity while reserving the right to poke under the hood when necessary. This has led me to Rust and I find it to be the better natively compiled strongly & statically typed language, but YMMV of course."[1]<p>(No, the concepts I learn in C++11 and beyond won't go into waste even when C++ becomes less and less relevant in a couple of decades.)<p>According to Stroustrup himself[2], you should know 5 different kinds of programming languages. So for me it's:<p>- Systems programming: C (has a special place in my heart)<p>- General purpose: C++ (will switch over to Rust when the time is ripe)<p>- Scripting: Python<p>- JVM: Scala<p>I think with these, you are well-equipped for the "future".<p>Also, specialization has its benefits[3], that's why I am not "language hopping" constantly.
I am "conservative" (C++) until I feel I that the time is right for me to be a "liberal" (Rust).<p>References:<p>[1] <a href="https://news.ycombinator.com/item?id=24805717" rel="nofollow">https://news.ycombinator.com/item?id=24805717</a><p>[2] <a href="https://youtu.be/NvWTnIoQZj4" rel="nofollow">https://youtu.be/NvWTnIoQZj4</a><p>[3] <a href="https://news.ycombinator.com/item?id=26119087" rel="nofollow">https://news.ycombinator.com/item?id=26119087</a>