this post was submitted on 14 Aug 2025
294 points (96.2% liked)

Programmer Humor

25730 readers
1229 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
 
you are viewing a single comment's thread
view the rest of the comments
[–] Lemminary@lemmy.world 23 points 1 day ago (14 children)

That's TypeScript. I can tell by the pixels defining a type above.

[–] Maiq@lemy.lol 6 points 1 day ago (13 children)

Was looking at it and could not figure out why their weren't any semicolon's.

[–] ScintillatingStruthio@programming.dev 13 points 1 day ago (12 children)

Neither Javascript nor Typescript require semicolon, it is entirely a stylistic choice except in very rare circumstances that do not come up in normal code.

[–] Maiq@lemy.lol 4 points 1 day ago (2 children)

That's good to know. Don't know how I didn't know this. Been writing JS since 2000. Always just used them I guess. Ecmascripts look funny to me without them

[–] ScintillatingStruthio@programming.dev 2 points 6 hours ago* (last edited 6 hours ago) (1 children)

Fair enough, I like it better without but I don't have a strong preference and have no issue adapting to whatever the style of the repo is.

I learned about it researching tools to automatically enforce formatting style and came across StandardJS, which eliminates them by default.

[–] Maiq@lemy.lol 1 points 6 hours ago (1 children)

I can see the benefit of matching style when working with others. I only code for myself and never had to worry about conformity for project consistency.

It is good to learn new things.

I'm sure I have some coding habitats that would annoy others.

Consistent styling helps make the actual meaningful changes easier to spot. Probably also useful for your own commit history when working solo in a repo, but most useful in a team, yeah!

[–] Lemminary@lemmy.world 3 points 1 day ago

Same here. My brain interprets them as one long run-on sentence and throws a parsing error.

load more comments (9 replies)
load more comments (9 replies)
load more comments (9 replies)