this post was submitted on 14 Aug 2025
274 points (96.3% liked)

Programmer Humor

25705 readers
1392 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

founded 2 years ago
MODERATORS
anzo@programming.dev
Feyter@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
274
True crime (europe.pub)
submitted 23 hours ago by tfm@europe.pub to c/programmer_humor@programming.dev
49 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] Lemminary@lemmy.world 9 points 18 hours ago* (last edited 18 hours ago) (2 children)

Explanation for nerdsThe reason is the JS compiler removes whitespace and introduces semicolons only "where necessary".

So writing

function myFn() {
  return true;
}

Is not the same as

function myFn() {
  return 
    true;
}

Because the compiler will see that and make it:

function myFn() { return; true; }

You big ol' nerd. Tee-hee.

[–] Ephera@lemmy.ml 7 points 17 hours ago

That's terrifying, especially in JS where no type system will fuck you up for returning nothing when you should've returned a boolean.

[–] exu@feditown.com 3 points 15 hours ago (1 children)

Common JavaScript L

[–] Lemminary@lemmy.world 1 points 12 hours ago

Not wrong, but funnily enough, it's a linting rule win. I'd go nuts if I didn't have my type checks and my linters. My current L, though, is setting up the projects initially and dealing with the configuration files if I raw dog it, but that's a problem with ESLint configs and the ecosystem as a whole having to deal with those headaches. So in the end, the JS devs got clever and shifted the blame to the tooling. 😅