this post was submitted on 02 Feb 2024
9 points (100.0% liked)

Programmer Humor

32400 readers
432 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
top 17 comments
sorted by: hot top controversial new old
[–] [email protected] 4 points 9 months ago* (last edited 9 months ago) (2 children)

Go is like snakes: you're hatched from an egg and pretty much effective from the get-go. The older you get, the bigger prey you can eat, but otherwise things don't change much since you were hatched. Your species can thrive in almost any environment, you're effective, you have all the tools you need straight out of the egg.

Rust is like humans. There's a huge incubation period, and you're mostly helpless when you're born, but the older you get, the more effective you become with the tools nature graced you with. And you, like Thanos, are inevitable, even if it does mean the death of billions.

Python is like beaver. Everyone has an opinion about you: some think you're cute, some think you're wierd. You're perfectly suited to your environment, but things get awkward outside of your natural habitat - you can function, but not as well as when you're in your comfort zone. And when people encounter you where they're not expecting, they can be unpeasantly surprised, and you can cause them trouble.

C++ is like platypus. You resemble some other more simple, some might say sane, animal, but developed into a sort of frankenstein monster creature made from a jumble of parts and a stinger that, when it kills someone, comes as a shock. Every part of you serves some purpose, even if it seems tacked-on and out of place.

Then there's Node. You are everywhere. You are legion. You fill up ecosystems. People try to defend you, claiming that you serve some purpose in the foodchain, but there's scant evidence. Attempts to eradicate you fail. You often spread deadly disease. You breed, rapidly, persistently, relentlessly. You are widely hated, and yet everwhere.

Edit: typo

[–] [email protected] 2 points 9 months ago* (last edited 9 months ago)

In other words, node = mosquitoes or invasive ant species?

[–] [email protected] 1 points 9 months ago* (last edited 9 months ago)

So then I guess C is salamander. Also lays eggs and lives by a pool, but doesn't do anything extra, and is a necessary step before most of the other modern languages.

COBOL is a coelacanth. To everyone's surprise, they're still out there. We thought they were an old, very extinct example of a non-terrestrial lobe-finned fish, but they actually hung on in some odd environments. They cause massive indigestion to anyone that has to consume them.

If Node is a mosquito, Javascript itself is another hymenopteran: the yellow jacket wasp. Just as hated, and with a tendency to injure handlers, but widely successful and defended as filling an actual useful role in nature. They build delicate, arguably pretty nests.

[–] [email protected] 1 points 9 months ago (1 children)

C holding a gun: "if you segfault it's your own fault"

[–] [email protected] 1 points 9 months ago

Assembly (Octopus swimming alone since birth): "compiler? what's a compiler"

[–] [email protected] 1 points 9 months ago

Forgot a semicolon? That's 200 errors

[–] [email protected] 1 points 9 months ago

Rust: “Oh honey you aren’t ready to compile that yet”

[–] [email protected] 0 points 9 months ago (2 children)

I would swap Python with C++. Constantly dealing with stupid runtime errors that could’ve been easily captured during compile time.

Did you forget to rename this one use of the variable at the end of the program? Sucks for you, because I won’t tell you about it until after 30 minutes into the execution.

[–] [email protected] 1 points 9 months ago* (last edited 9 months ago) (1 children)

you need a linter, bro

when integrated into the editor it'll highlight stupid mistakes as they're typed

I recommend Ruff for real time checks, and pylint if you need a comprehensive analysis.

[–] [email protected] 0 points 9 months ago (2 children)

sure, but thats just outsourcing the problem.

[–] [email protected] 1 points 9 months ago

It's also a solution...

[–] [email protected] 1 points 9 months ago* (last edited 9 months ago)

As if that's a bad thing... it means you're not locked in with a tool you don't like and the language itself doesn't dictate your workflow.

There's very little benefit and a lot of potential problems in using a single tool for everything.

[–] [email protected] 0 points 9 months ago (1 children)

My brother. That's why you do unit tests.

[–] [email protected] 1 points 9 months ago (1 children)
[–] [email protected] 1 points 9 months ago

👆 definitely linting first 👆

finding errors as you type is even better than finding errors at compile time

[–] [email protected] 0 points 9 months ago (1 children)

C++ and C compilers are much more friendly now a days

[–] [email protected] 1 points 9 months ago

can't wait to use templates and have the compiler spit out a 120 page autobiography