No, the C++ should fear you!
this post was submitted on 02 Nov 2026
46 points (100.0% liked)
Programmer Humor
33931 readers
767 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
- If the mod doesn't find it funny, you're banned. Ha-ha!... For real: do not use the community for "statements". There are other places for such content. Keep it chill and funny.
founded 3 years ago
MODERATORS
Less fucked-up than Javascript.
This diagram is nonsense. JavaScript programmers know to simply never use == but to use === instead. Half of JavaScript is like this. Oh, there's a feature, but it behaves in a super weird way so we don't use it to avoid the weirdness.
Where's the >== operator? Because they also have the exact same problem.
The recommended ESLint rules catch most of the bad stuff, and these days this is all you need in your ESLint config to enable them:
import {defineConfig} from 'eslint/config';
import js from '@eslint/js'
export default defineConfig([
js.configs.recommended,
];
There's one use case where == is still commonly used: == null matches both null and undefined. Lint rules that block == usually allows the null case as an exception.
I wonder how much bandwidth is wasted on the extra =, since it survives minification 😅
Gzip (any properly configured static server will serve compressed assets) probably compresses them down so probably a single extra byte per file
But if every single comparison used in a file is a triple =, then any compression algo worth its weight in salt will compress that bloat away during transmission
The real issue is all the precious precious RAM those extra = use on the client device once received and unpacked!
IIRC modern linter rulesets generally just outright error if you do anything remotely like this.
For those needing help the code is:
using namespace std;
int main()
{
while (true)
{
cout << 'e';
cerr << 'e';
}
return 'e';
}
Anyway, my opinion: c is the best thing to ever exist, and c++ is evil
No. I don't find it a particularly nice language to work with, but there's no reason to fear it. Just make sure you know what you're doing if/when you use it.
So yes
No