this post was submitted on 16 Mar 2025
4 points (100.0% liked)

Programmer Humor

22347 readers
2603 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
4
C++ (ani.social)
submitted 4 weeks ago* (last edited 4 weeks ago) by kiri@ani.social to c/programmer_humor@programming.dev
6 comments fedilink hide all child comments
 

by trg_thanh

top 6 comments
sorted by: hot top controversial new old
[–] brucethemoose@lemmy.world 1 points 4 weeks ago* (last edited 4 weeks ago)

Meanwhile, Rust punches you in the face for the mere suggestion. Again. And again.

Python happily nods, runs it one page at a time, very slowly, randomly handing things off to a C person standing to the side, then returns a long poem. You wanted a number.

Assembly does no checking, and reality around you tears from an access violation.

EDIT: Oh, and the CUDA/PyTorch person is holding a vacuum sucking money from your wallet, with a long hose running to Jensen Huang's kitchen.

[–] count_dongulus@lemmy.world 1 points 4 weeks ago

This is why I will never touch Javascript again. Long ago when I worked on web stuff, half my workflow was spent in the debugger tracing garbage to find where a typo was. The industry moved to Typescript, and now assuming the strictness checks are enabled, if some Typescript transpiles successfully, I can be 95% sure whatever fuckup I observe at runtime is a logic problem.

Weakly typed languages were an awful idea. But in general, if the compiler isn't able to detect most runtime issues (like with C++ here), it's not going to be the most productive language to use for building solutions compared to smarter alternatives.

[–] ICastFist@programming.dev 1 points 4 weeks ago (2 children)

What surprised me the most was the speed of the compilation, must be a very small program. I tried to compile Godot from source once. Force-stopped it after 3 hours

[–] scholar@lemmy.world 1 points 4 weeks ago

There's a reason the play is called waiting for Godot

[–] Sylvartas@lemmy.dbzer0.com 1 points 4 weeks ago

How many cores do you have and what compiler was it ? Also RAM can help with huge codebases iirc. When I was working with UE5 I had the best Ryzen available with 128 Go of RAM, could compile the engine (which is much bigger than Godot) from source in less than 2 hours iirc (yes that is a full clean+rebuild, not just compiling recent changes)

[–] henfredemars@infosec.pub 1 points 4 weeks ago

Ah, C++. An endless supply of footguns where the difference between a junior and a senior dev is knowing what parts of the language to never use.