4 ms·
I'm similarly irked when people say "C/C++" and I would prefer that people not confuse the two. I used to say "C/C++" before I gained sufficient knowledge to un
by optymizer 3y ago
I'm similarly irked when people say "C/C++" and I would prefer that people not confuse the two. I used to say "C/C++" before I gained sufficient knowledge to understand the differences between the two languages, so if you say "C/C++" I know you're not an expert in either.
Admittedly, the author did a phenomenally poor job at highlighting the differences that people should care about. Nobody cares about casting malloc or K&R syntax. People do care about compilation time, binary size, strong type systems, name mangling, debugging, complexity, error messages, embedding etc.
Technical discussion aside, I'm saddened by the dismissive nature of the comments. Even if you're not at a point where you can internalize why someone else is asking to stop saying "C/C++", the unempathetic nature of the comments is discouraging.
- foul 3y ago>People do care about compilation time, binary size, strong type systems, name mangling, debugging, complexity, error messages, embedding etc Not the author but I sense that going down that road there is risk of derailing into which lang is best.
- optymizer 3y agoI can see that happening, and I would frame it as a choice rather than absolute truths, i.e. "this set of strengths of C" vs "this other set of stregths of C++". Imo the sets are disjoint enough that "C/C++" is doing the users of both languages a disservice, but convincingnothers of this does require a better essay.