>we should also make a list of all languages I don't like
Not really, no one's interested in your opinion.
/dpt/ - Daily Programming Thread
considering it's what you/he did, it's only fair.
>C
>decrepit
Too brainlet for manual memory management detected.
This is an abuse of overloading. Don't do this.
Not really, I like many languages on that list. But let's face it, none of them have any real world relevance.
>C is the only language with MMM
literally all those langs except maybe idris are used by actual companies.
Why?
>What if you have operator== that returns true for two different arguments?
Define different.
Overloading in general is dangerous because it encourages you to write code which does different things for different types. Overloading on reference-ness just makes it even more opaque and unpredictable.
What is the goal you're trying to accomplish?
Desu I'm not sure. But to me it seems like an excuse for the language.
I read the Twitter thread where they tried to clarify just recently. But after reading that I get the sense that was mostly an attempt to cover their own ass in making that statement. I would expect this view to come from someone working in an environment where launching a debugger is just not feasible. Problems are discovered latent and the software needs to be run as a live service to find most bugs.
To forgo program state inspection in C/C++ as a language principle is foolish. And usually when we're talking about debuggers that's the primary thing people think about. Not program tracing.
If you're only doing program tracing you could probably do without a debugger.