How is it licensed, Jigsaw? Eh? What distro is it from? Is that a fucking Snap wheel?
Programmer Humor
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
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
Snap
Ok, this set me off.
What I hadn't anticipated in my 20 years away from Linux was not only had teams of unpaid volunteers been beavering away behind the scenes to make everything work better, other much more enthusiastic teams have been thinking up new and exciting ways to break it again.
Reinventing the wheel leads to a profound understanding of why wheels are round.
That's what documentation is for.
Documentation is written exclusively for people with PhDs.
Well, it would have been if people updated it when making changes; now it's just all an incorrect snapshot of an older version of wheel that no longer reflects reality.
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.
The Wheel weaves as The Wheel wills.
Use the -w
flag and the wheel will weave as you will.
Wtf did not expect a Wheel of Time reference lmao
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!
"I WOULDN'T BE REINVENTING IT IF THEY DIDN'T FORCE ~~systemd~~ AXLES ON EVERY WHEEL!!!"
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?"
but is it written in 6510 assembly, with cool graphics and catchy music with fast arpeggios?
This is a poorly designed horror trap. Here, let me help you!
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.
I think we need to take a bit of a step back and consider what kind of shed we might use to store this wheel...
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?
It works fine. It's a perfectly good wheel.
Hey where is Underwaterbob?
He's trapped in that Jigsaw room.
The door is unlocked though?
Yeah, but there is a wheel in there and UWB won't leave until he figures out if there is a way to improve it.
Has any one asked him to?
No
Will he get paid to improve it?
No
What does the wheel do?
You roll it out of the way so you can exit the room.
sudo systemctl stop sawtrapd
And don't forget
systemctl disable sawtrapd
so it won't restart again.
sysyemctl disable --now sawtrapd to do both in one command.
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?
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.
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?
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."
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. >:(
Here's the real question... What licenses are the wheel and door using?
Is the wheel FOSS? No? Guess I have to then.
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
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...
As if I don't have a stash of previously reinvented wheels to choose from in my personal code. Buuuut, who can resist reinventing the wheel for the 25th time?
But my wheel will be much better. I will start from the center with a very simple skeleton and build on top of it as needed. It will be very modular, elegant and easy to understand. It will be my masterpiece.