4 ms·
you may have replied to the wrong thread. But I'd like to point out that while Google has some of the top C++ experts working for them, is heavily involved in
by flipgimble 7y ago
you may have replied to the wrong thread.
But I'd like to point out that while Google has some of the top C++ experts working for them, is heavily involved in C++ standardization and compiler writing process, in 2016 they claimed to have 2 billion lines of C++ running their infrastructure...
.. and yet they don't suffer from familiarity bias or the sunken cost fallacy I hear in your comment.
Instead Google C++ developers are sounding an alarm over the future direction the language and its crippling complexity:
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p2137r0.html http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p213...
- pjmlp 7y agoGoogle is also known for having brain dead guidelines for C++, that speak against community best practices. Just like with Go, their monorepo and internal tooling deturps the understanding how everyone else actually uses C++.