You must log in or # to comment.
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??
Military-grade.
*passes Valgrind*
rust is a terrible material for wheels. Corrosion is not usually a good thing.
You just have to rebrand it as “iron-based ceramic”.
How is it licensed, Jigsaw? Eh? What distro is it from? Is that a fucking Snap wheel?
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.
Just putting the finishing touches on GNAW (Gnaw’s Not A Wheel)
sudo systemctl stop sawtrapdAnd don’t forget
systemctl disable sawtrapd
so it won’t restart again.sysyemctl disable --now sawtrapd to do both in one command.
Here’s the real question… What licenses are the wheel and door using?
The door is obviously open. Not sure about the wheel, though…
Developer: Kill me if you must but i’ve turned the wheel into a modular service called systemd-wheel
Investor: Can the wheel be made into a subscription service?
Consumer: It say’s here I can subscribe to ‘Wheel Pro’ for only $69.99/month and I will automatically receive all the latest features the second they come out!
Noob: I just use WIMP, it’s free and does 99% of what Wheel Pro does. I don’t need all those extra features.
Consumer: Psh, WIMP is ugly and you can’t even adjust the tire pressure by millipascals.
Noob: They added that feature in March.
Consumer: I NEED IT FOR WORK OK!
GNOME developer: “Stop forcing us to use wheels! Why can’t you just import GTK in your project?”
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.
That involves knowing how to read
Not necessarily.
“I WOULDN’T BE REINVENTING IT IF THEY DIDN’T FORCE
systemdAXLES ON EVERY WHEEL!!!”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?
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.
All those wheels made without any unit tests. What was humanity thinking?
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
-wflag and the wheel will weave as you will.
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.
I woulda tried them on JSON. As long as they use an editor that keeps track of nested brackets I think it’s much more natural than XML.
I switched to TOML for my stuff.
Sounds ini to me.
I’m thinking WaaS
This is a poorly designed horror trap. Here, let me help you!
