You find a predefined foot shooting function, but it’s marked as unsafe and someone forgot to document what the safety contract was. You write up an unsafe block anyway and pass that function ownership of a bullet and a mutable reference to your foot, and get a segfault.
You search crates.io for “gun” and find a crate called pewpew. It looks incredibly spiffy. It supports manual or automatic operation, being used with or without a turret (or on a user-supplied turret) and with any number of middlewares for storing the bullets and transforming them on their way to the firing chamber. Unfortunately you can’t shoot yourself with it because your foot doesn’t implement the relevant autotraits.
Systemd:
You create a service file for shooting yourself in the foot and set it to run at system startup. It seems to work, but after a cold boot, sometimes your foot has a hole in it and sometimes it doesn’t. After hours of debugging, you discover that this is because sometimes the gun service starts up and fires its bullet at nothing before the foot service finishes initializing and puts itself in the way. To resolve this you will likely need to edit the source code of your foot to make it support systemd-notify.
It is indeed a trope and a mostly false one - C++ introduces more dramatic ways to footgun yourself but a plethora of tools to make it easier to avoid them - in particular the built in library functions actually encourage good C++ programming practices…
Learning about reflog was a game changer. Now I’m never afraid of breaking my branch. If I mess up, I can always git reset —hard to a previous state.
Another game changer was learning that a perfectly valid way of doing squash is to do git reset to an earlier commit and then do git commit -a. Saves a lot of rebasing headache.
With C, you need to carefully craft your own gun with just iron ingots and a hammer. You will shoot yourself in the foot, but at least you’ll have the knowledge that it was your craftsmanship that led to it.
With C++, there are already prebuilt guns and tons of modifications that you can combine at will. If you shove it in the right way, you can make a flintlock shoot a 50 cal, but don’t complain when your whole leg gets obliterated.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
This is why I stick to Rust. The gender affirming surgery takes some getting used to, but at least I have both legs.
Don’t waste money on HRT, use Rust and your private parts will rust away in no time.
Mine disappeared already, but I just used C all the time. Maybe the femboy clothes and tailplug helped?
Enjoy your government mandated Blahaj shark
He forgot to allocate his leg.
Also, it looks like he pointed to foot correctly. I’m surprised he didn’t shoot his hand, the pointer to a pointer to a foot.
This joke has layers, is quite funny, and kind of hurt. Just like my pointer handling code!
no foot to shoot, no problem! 👍
Always a fun read.
The Apache 404 page doesn’t really seem that interesting.
The URL is http://toodarkpark.org/computers/humor/shoot-self-in-foot.html and it loads / reloads fine. I don’t know what else to tell you.
Your browser is trying to load the https version. Try with http.
We need an updated version
Rust:
pewpew. It looks incredibly spiffy. It supports manual or automatic operation, being used with or without a turret (or on a user-supplied turret) and with any number of middlewares for storing the bullets and transforming them on their way to the firing chamber. Unfortunately you can’t shoot yourself with it because your foot doesn’t implement the relevant autotraits.Systemd:
I’ve heard this trope before but I’m skeptic. I’m not a C expert but I can’t believe memory bugs in that language are so much more benign than in C++.
It is indeed a trope and a mostly false one - C++ introduces more dramatic ways to footgun yourself but a plethora of tools to make it easier to avoid them - in particular the built in library functions actually encourage good C++ programming practices…
Well, let’s just ignore
gets().They are, but it’s also more than that. C++ is like if git were a programming language.
Yep. Incredibly powerful, and it will not hesitate to help you blow your own legs off.
The big difference is that git will save your legs in
reflogfor a couple of weeks.Learning about reflog was a game changer. Now I’m never afraid of breaking my branch. If I mess up, I can always
git reset —hardto a previous state.Another game changer was learning that a perfectly valid way of doing squash is to do
git resetto an earlier commit and then dogit commit -a. Saves a lot of rebasing headache.Interesting analogy, please explain
With C, you need to carefully craft your own gun with just iron ingots and a hammer. You will shoot yourself in the foot, but at least you’ll have the knowledge that it was your craftsmanship that led to it.
With C++, there are already prebuilt guns and tons of modifications that you can combine at will. If you shove it in the right way, you can make a flintlock shoot a 50 cal, but don’t complain when your whole leg gets obliterated.
Memory bugs are only a tiny share of the foot guns in C++