3 ms·
The culmination of your message was "Let's just collectively admit it, finally - you can't write safe C++ in a codebase this complex.", that's your point. It's
by blub 8y ago
The culmination of your message was "Let's just collectively admit it, finally - you can't write safe C++ in a codebase this complex.", that's your point.
It's probably correct, but also meaningless as I mentioned, because:
a) most codebases aren't even nearly this complex
b) no one will likely write such a codebase again
So the entire "point" is just trivia. It can't be used to decide whether to program something in C++, it can't be used to decide whether to use Chrome, it's not actionable at all.
Frankly I'm peeved that a superficial comment triggered such a long discussion and monopolised the top spot in the thread instead of making space for technical explanations or more interesting discussion.
- staticassertion 8y agoYou're attempting to derive meaning from my post, which in your mind is that browsers should not use C++, where there is no such meaning. That you have failed to do so is not my issue. Don't blame me for having an upvoted post.