C++ is special because it combines two big ideas:
- Zero-cost abstractions (you only pay for what you use)
- High-level abstractions (OOP, lambdas, code-generation, etc. )
I would jump straight to C++ 17. It looks completely different to early 2000s C++ and makes functional programming easier (type inference, lambdas, constexpr, etc. ).
If you learn to use C++ well, you will be able to write faster code faster.
I'd love to, but there are simply no (accessible?) resources. I'd love a "how to write C++17 with no baggage" book, but it simply doesn't exist. (please, correct me if I'm wrong?)
I really want to get to know C++, it looks like it's become a fantastic language, but in all seriousness, I could write fast, performant robust Go within a weekend, I'm proficient in half a dozen other languages, and C++ programmers still unironically suggest a stack of books the height of a small table to beginners.
The Book is intended for all C++
developers, regardless of their experience. The
beginner and intermediate developers will benefit
the most from the book in their attempt to become
prolific with C++.
Experienced C++
developers, on the other hand, will find a good
reference for many C++11, C++14, and C++17
language and library features that may come in
handy from time to time.True in theory and essentially because C++ still remains mostly a superset of C, but unfortunately the majority of C++ programmers I've met tend to overabstract and not realise it, making this claim not really true in practice.
High-level abstractions (OOP, lambdas, code-generation, etc. )
On the other hand, this is definitely true in practice.
I think this notion is out-of-date. Have a look at this slide: https://youtu.be/_wzc7a3McOs?t=21m37s It shows how C++ has evolved away from just "C with Classes".
I agree that many C++ programmers over-abstract things.
I meant that C code, with few modifications, will basically work fine when compiled with a C++ compiler.