Eh, no. This is pedantic for the sake of pedanticness - or actually, for the sake of making a pointless argument. There are contexts where "C/C++" makes sense,

Eh, no. This is pedantic for the sake of pedanticness - or actually, for the sake of making a pointless argument. There are contexts where "C/C++" makes sense, sure something like "program Foo is written in C/C++" usually doesn't make much sense (though it can make sense if it is written in both languages - i.e. using both C and C++ modules) but something like "program Foo is a C/C++ code generator" (think something like a generator for header files for example) in that the code it generates can be compiler as either C or C++. After all, unlike Rust, Go and Kotlin mentioned in the article, C and C++ do share a sizable common subset (heavily biased towards the C side of course). This is why C header files can often used as-is in C++ or with the minor modification based on the __cplusplus macro. Language is meant to be parsed by humans, not computers and humans can take context into account (and with the recent developments in AI even computers can do that too :-P).