this post was submitted on 02 Feb 2024
1027 points (98.3% liked)

Programmer Humor

31793 readers
217 users here now

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

Rules:

founded 5 years ago
MODERATORS
 
top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 152 points 6 months ago* (last edited 6 months ago) (6 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] 41 points 6 months ago* (last edited 6 months ago) (3 children)

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

[–] [email protected] 22 points 6 months ago (2 children)
[–] [email protected] 7 points 6 months ago (1 children)

Roaches don't spread nearly as much disease as 'squiters, and IIRC are actually important in some ecosystems.

load more comments (1 replies)
load more comments (1 replies)
load more comments (2 replies)
[–] [email protected] 20 points 6 months ago (1 children)

These are excellent.

I need to add Perl.

Perl is a honey bee. You are unassuming and pragmatic. You fill every niche. Your buzzing carries meaning, but only to other bees. In theory, your ecosystem niche is filled by many competing solutions that are more fit to purpose. But somehow we all know in our hearts that if you disappear, all life on the planet will probably die soon after.

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

May I acquaint you with the Evil Mangler, historically used by GHC to compile Haskell via C. It would go through the assembly gcc generates and rearrange whole blocks and deletes instructions, such as function prologues and epilogues.

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

Holy shit. This thing sounds insanely awesome, but also quintessentially Perl. Like, the perfect holotype for Perl.

And, damn, but I'm impressed. I've seen code that I admired; elegant, inspired, wise code... but the Evil Mangler leaves me in awe.

load more comments (1 replies)
[–] [email protected] 20 points 6 months ago* (last edited 6 months ago) (4 children)

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] 6 points 6 months ago

I especially enjoyed your COBOL metaphor. Nicely done!

load more comments (3 replies)
[–] [email protected] 12 points 6 months ago

Node: You fill up ~~ecosystems~~ hard drives.

load more comments (1 replies)
[–] [email protected] 104 points 6 months ago (2 children)
[–] [email protected] 33 points 6 months ago

C++ compiler:

Error: missing ';' on line 69

Warning: two statements on same tabulation depth after if without curly brackets on line 123. Are you sure you want this?

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

Sql errors: there be a syntax error roughly over there I think. Or maybe it's a semantic error somewhere else I'm not entirely sure. Listen man all I can say is that this one comma there definitely has something to do with it probably, and the error is most certainly either to its left or to its right.

load more comments (1 replies)
[–] [email protected] 93 points 6 months ago* (last edited 6 months ago) (10 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] 47 points 6 months ago* (last edited 6 months ago) (2 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.

[–] darcy 17 points 6 months ago (2 children)

sure, but thats just outsourcing the problem.

[–] [email protected] 31 points 6 months ago

It's also a solution...

[–] [email protected] 19 points 6 months ago* (last edited 6 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.

load more comments (1 replies)
[–] [email protected] 20 points 6 months ago (17 children)

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

[–] [email protected] 31 points 6 months ago (1 children)
[–] [email protected] 17 points 6 months ago

👆 definitely linting first 👆

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

[–] [email protected] 7 points 6 months ago

But are you even a real programmer if you don’t test in production?

load more comments (15 replies)
[–] [email protected] 13 points 6 months ago* (last edited 6 months ago) (1 children)

You can solve this with git:

git gud

Seriously though, writing a monolith of a function and not testing anything until you run it the first time isn't the way to go. Even with a compiler you're only going to catch syntactical and type issues. No compiler in the world is going to tell you you forgot to store your data in the correct variable, although it or a a linter may have helped you realize you weren't using it anywhere else.

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

Python was typeless. And it was common to reuse variables with different types of content.

So you at some point never knew what actually is within the variable you are using.

Using typing in python solve 95% of your problems of having runtime errors instead of compile errors

load more comments (1 replies)
[–] [email protected] 6 points 6 months ago (1 children)

I mean, is C++ any better? Sure, it catches some errors at compile-time, but others can turn into undefined behavior pretty easily.

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

Catching some errors is better than catching no errors. No compiler in any language can protect you from all runtime errors either way, but some are better at it than others.

load more comments (1 replies)
load more comments (6 replies)
[–] [email protected] 42 points 6 months ago (2 children)

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

load more comments (2 replies)
[–] [email protected] 34 points 6 months ago (1 children)

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

[–] [email protected] 12 points 6 months ago

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

[–] [email protected] 20 points 6 months ago (3 children)

If you're using C++, why not use streams?

[–] [email protected] 16 points 6 months ago (5 children)

Yes, fprintff is a C thing.

load more comments (5 replies)
load more comments (2 replies)
[–] [email protected] 16 points 6 months ago* (last edited 6 months ago)

Use streams, or fmt. fprintf is for C. It's like people buying a cheap android phone, then going for an iPhone.

I don't blame you though, C++ carries a lot of baggage. Modern C++ is pretty nice, though, as is Rust.

[–] [email protected] 8 points 6 months ago

And there's haskell compiler

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

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

[–] [email protected] 15 points 6 months ago

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

[–] [email protected] 7 points 6 months ago* (last edited 6 months ago)

A quick -Werror=format -Werror=format-nonliteral -Werror=format-security will solve all your printf woes.

[–] [email protected] 6 points 6 months ago

@stsquad
— Is my program about 1,000 lines complex?
— Yes, sure!
— Here you are my about 1,000 lines of 'printf("Hello, World\n");'.

[–] [email protected] 6 points 6 months ago

The meme will be completely different after writing a few lines of rust for a week 😹

load more comments
view more: next ›