I bet the wheel would be better if it was written in Rust.
(Disclaimer: I have never actually written Rust.)
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.
I bet the wheel would be better if it was written in Rust.
(Disclaimer: I have never actually written Rust.)
Hello, Rust developer. [My name, etc.] It works fine, and is written in C++. [Rest of challenge is the same.]
Truly diabolical
But it's not memory safe!!
I know!! How can Jigsaw claim it "works fine"? He'd probably say something like "it's battle-tested and state of the art." What does that even mean??
rust is a terrible material for wheels. Corrosion is not usually a good thing.
Look, I'm not saying the wheel is wrong. It rotates, but what if two people try to turn the wheel at the same time, in opposite directions?
What if—instead of risking misuse of the wheel—we have a my_wheel::Wheel
, which only one person can rotate at any given time? The multiverse could enforce this safety at compile time by making it impossible for there to exist a universe where two people both think they own the right to rotate the wheel. In fact, it could even make it impossible for me to lend out the wheel to more than one person at a time.
And, maybe... we could make the wheel even better. Cars rest on top of wheels, sure. But what if I wanted to make a car that rests on top of other cars? If we rotate the super-car's wheels, we don't want to make the sub-cars flap around—we want the sub-car wheels to rotate. It would be more future-proof to make a Wheel
trait, then to make RubberTyre
implement Wheel
. Then, if we ever needed to make cars into wheels, we could have them also implement Wheel
—but delegate the responsibility of rotating to their own wheels.
In fact, we should make it into a whole library. Our other projects could need wheels. Mr. Mittens might need them eventually!
Disclaimer: I have never actually written Rust.
neither have most of the people advocating for (or against) rewriting stuff in Rust lol
I'll have you know, I've started several projects in Rust!
Only to realize I don't have time to do unpaid work even if it IS fun.
Developer: Kill me if you must but i've turned the wheel into a modular service called systemd-wheel
GNOME developer: "Stop forcing us to use wheels! Why can't you just import GTK in your project?"
I have had plenty of suggestions to do very simple things in the games I mod to blow up the lines of code and do the exact same thing I already am doing, but in a more complicated, roundabout way that ends up working slower.
"Why are you spawning blank soldiers and then equipping them, instead of spawning already equipped soldiers?"
"Because I can only spawn soldiers already equipped with stuff from a pool of premade classes, and I want to customize their loadout. It also takes 5 minutes longer to load them in already equipped for some damn reason, whereas when I do it this way it only pauses the game for 10 seconds before it's good to go."
"... ARMA's engine sucks."
"Agreed."
You just gave me flashbacks to that abomination of a programming language they call sqf.
I hate for asking, but can you grace us with a hello world in squeef?
Here's the real question... What licenses are the wheel and door using?
The door is obviously open. Not sure about the wheel, though…
And remember open does not imply free
I bet it uses ffmpeg...
I read that as ffmpreg, and I thought it was some new ao3 trope where two girls impregnate a guy or something.
No no, ffmpeg is completely different! It refers to two women pegging a man.
That is horrible! How ridiculous and just horrible! What’s the url so I know what to stay away from?
Least brainrotted fediverse user
Does the wheel fall under any cumbersome non free licenses or patents? If I want to modify this wheel to suit my needs, then share that work and information with others, am I free to do so?
How is it licensed, Jigsaw? Eh? What distro is it from? Is that a fucking Snap wheel?
We'd rather re-create reality where we know everything rather than taking the time to learn how to use a system someone else wrote.
IT and DevOPS does this too.
I worked with a group once that re-invented XML so that non-technical people could create text-based rules instead of writing code. But it ended up with a somewhat rigid naming structure with control characters and delimiters. The non technical people hated it more the actual XML they had used prior.
"Or as I've recently taken to calling it, saw plus trap"
I'd just like to interject for a moment. What you're refering to as wheel, is in fact, GNU/Wheel, or as I've recently taken to calling it, GNU plus wheel.
unjerk: pretty bold to compare software to a wheel. it's more so like some roughly rollable shape which is why some people think they can make it more rollable, and yes those people fail from time to time
Yes, let's not reinvent any wheels to save time and money. What? Why do you have to use three different screens from two different applications to get the information you need for one shipment invoice? Because we didn't reinvent any wheels. You're welcome.
One of the worst parts about this is that I would never have thought about reinventing it until he told me not to.
Bloody reverse psychology still working on me. >:(
Spent months setting up my home server with Docker containers while learning Linux. Everything worked perfectly fine.
Then I realised Ubuntu Server is just a Debian-flavored landfill. Switched to EndeavourOS. Everything worked perfectly fine.
Then I made NixOS my daily driver and thought, "Hey, let’s ruin my weekend." Migrated the server. Everything worked perfectly fine.
Found out I could run containers as systemd services. Replaced Docker out of sheer spite using compose2nix. Everything worked perfectly fine.
Then I heard btrfs was the bee's knees. Reformatted my drives, migrated again, and spent a week learning why subvolumes are better than sex. Everything worked perfectly fine.
Got a free MacBook. Slight hardware bump. Migrated again. Spent hours fighting T2 drivers while deepthroating Tim Apple's cock. Everything worked perfectly fine.
Rewrote every systemd service as NixOS modules. Why? Something something George Mallory. Everything still works perfectly fine.
Did I ever notice a difference from the frontend? Nope.
Was this a good use of my time? Fuck no.
Did it need to happen? Does the pope compile from source in the woods?
There is a whole extra spoke in the wheel. Look, I'm not gonna reinvent it... I just... need to... adjust some values... and there! Look, its fine.
Wait.
Why is it wobbling like that?
Hold on, I just need to get rid of this other spoke...
Reinventing the wheel leads to a profound understanding of why wheels are round.
So, your plan is to kill people of starvation and sleep deprivation?
The wheel has had a number of innovations over the years. The earliest wheels were flat disks of wood that were heavy and slow turning. The Romans invented spokes and metal rims which made them faster, more durable, and gave them more traction. Questions we need answered: What is this wheel in particular designed to do? Is there any way we could make it work more efficiently at its task? Do we value performance over reliability, or vice versa? Etc. Etc.
All those wheels made without any unit tests. What was humanity thinking?
Hmmm what if this wheel could roll itself? If we use the power of 7 suns we could put ~~AI~~ cocaine in it.
Have you ever used wheel-el in emacs? It really sets a high bar.
Listen here, "bro". "Fine" is well below my standard, ok?? The world wasn't built on "fine", now was it? No! It wasn't! ᶠᶦⁿᵉ ᶦˢ ⁿᵒᵗ ᵍᵒᵒᵈ ᵉⁿᵒᵘᵍʰ ᶠᶠˢ ⁻⁻⁻ ⁻⁻ ⁻⁻⁻⁻ ⁻⁻⁻⁻ ⁽ᵗʳᵃᶦˡᶦⁿᵍ ᵐᵘᵐᵇˡᵉˢ⁾
"I WOULDN'T BE REINVENTING IT IF THEY DIDN'T FORCE ~~systemd~~ AXLES ON EVERY WHEEL!!!"
Joke's on you, the wheel was reinvented plenty of times.
This is a poorly designed horror trap. Here, let me help you!
Not even in programming but I'd have to at least test the wheel see if it's as good as I'm told