Programmer Humor

34043 readers

1339 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

anzo@programming.dev

Feyter@programming.dev

BurningTurtle@programming.dev

pylapp@programming.dev

194

Is my fear of C/++ Justified? (quokk.au)

submitted 1 week ago by Solrac@quokk.au to c/programmer_humor@programming.dev

37 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] grue@lemmy.world 94 points 1 week ago (22 children)

Less fucked-up than Javascript.

[–] NateNate60@lemmy.world 44 points 1 week ago (20 children)

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.

[–] dan@upvote.au 13 points 1 week ago (2 children)

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.

[–] BradleyUffner@lemmy.world 13 points 1 week ago* (last edited 1 week ago)

So you're saying the jank has become structural?

[–] Venator@lemmy.nz 4 points 1 week ago (2 children)

I wonder how much bandwidth is wasted on the extra =, since it survives minification 😅

[–] ignotum@lemmy.world 7 points 1 week ago

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!

[–] 9point6@lemmy.world 3 points 1 week ago (1 children)

Gzip (any properly configured static server will serve compressed assets) probably compresses them down so probably a single extra byte per file

[–] dan@upvote.au 3 points 1 week ago* (last edited 1 week ago)

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.

load more comments (17 replies)

load more comments (18 replies)