188
Is my fear of C/++ Justified?
(lemmy.nz)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 02 Nov 2026
188 points (97.5% liked)
Programmer Humor
33973 readers
225 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
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:
There's one use case where
==is still commonly used:== nullmatches bothnullandundefined. Lint rules that block==usually allows thenullcase as an exception.So you're saying the jank has become structural?
I wonder how much bandwidth is wasted on the extra
=, since it survives minification ๐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!
Gzip (any properly configured static server will serve compressed assets) probably compresses them down so probably a single extra byte per file
Gzip is old-school. The majority of modern sites use Brotli now. It's slower to compress, but that's not normally an issue for static resources (CSS, JS, etc) because they can be pre-compressed during the build and the web server serves the pre-compressed files instead of dynamically compressing them.