The author claims that the C++ type system blows goats dick, the burden is on them to actually prove their point besides using middle school recess vocabulary.
The author claims that the C++ type system blows goats dick, the burden is on them to actually prove their point besides using middle school recess vocabulary.
No, he doesn't. He claims that the Macro system does. And he's right, C macros are full of well documented pitfalls [1][2], especially when compared to other languages. This is not really a controversial claim, btw. At this point this is common knowledge. "Blows goats dick" is letting it off easy, even. It only implies low quality, or difficult to use. C Macros however can be dangerous, unsecure and misleading. Also, this is an informal talk. Sure, you might take issue with his language, but I would expect someone taking issue with the claim to at least know about the general consensus on the topic.
[1] https://gcc.gnu.org/onlinedocs/cpp/Macro-Pitfalls.html
[2] https://www.brainbell.com/tutors/c/Advice_and_Warnings_for_C...
The reasoning has the potential to change the way you think about his claim or it has the potential to be completely wrong. But the context of the situation makes it so that you cannot ignore the potential.