3 ms·

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

• SiempreViernes 8y ago
  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 8y ago
    > 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 https://google.github.io/styleguide/cppguide.html [2] https://google.github.io/styleguide/cppguide.html#Exceptions https://google.github.io/styleguide/cppguide.html#Exceptions
    • RcouF1uZ4gsC 8y ago
      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.