[RcouF1uZ4gsC]

I would be very wary of any Google material on C++.

Their C++ style has a heavy emphasis on pointers. In addition, their banning of exceptions warps their code in other ways (for example a heavy use of out parameters).

Also, they have a tendency to use their own alternatives to stuff in the standard library.

If you already know modern C++ you can discern the good advice from the bad/archaic advice, but if you are learning Modern C++, you would be best served by avoiding it.

[gaius]

That is the mistake I made in the 90s. I thought I was learning C++ but really I was learning MFC.

[shortoncash]

Agreed! The Google style guideline goes out of its way to inform people not to use templates too much, or something along those lines. It hints that those features are for language experts. This is bad advice, in my opinion and basically keeps you out of using the most useful features of the languages.

[matt_the_bass]

I think fundamental understanding of pointers is important to C++ and not we’ll understood by many people who come from a non-C/C++ background.

[sharpercoder]

Typically, I would agree. Yet, I'm fairly certain Google has good reason for doing so.

[SiempreViernes]

Sure, but do you know them? If you don't, how will you judge if their reasons are valid for you?

In any case, the simple fact that the reasons are unknown speaks pretty heavily for the case that the reasons aren't universally valid, so you would be learning a dialect of C++.

[davidcuddeback]

> Sure, but do you know them?

Google documented pros/cons and reasons for their decisions in their style guide, which is public [1]. Whether or not Google's final decision is applicable to you, reading the pros and cons is informative. For example, their reason for not using exceptions is specific to their existing code base [2], but the discussion is informative.

[1] https://google.github.io/styleguide/cppguide.html

[2] https://google.github.io/styleguide/cppguide.html#Exceptions

[RcouF1uZ4gsC]

Yes, the style guide is informative and Google does have reasons for doing things the way they do. However, they way they are doing things is decidedly not embracing Modern C++. Their teaching material will reflect their philosophy. Therefore, when you are learning modern C++, you should avoid their material. After you are comfortable with Modern C++, then you will have the perspective to differentiate the good advice applicable to you.