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”.
I shudder at the thought of potholes.
I guess we’ll have to reinvent a pneumatic tire as well to protect it.
I think they mean to write the word “wheel” into surface rust.
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
Wheeltrait, then to makeRubberTyreimplementWheel. Then, if we ever needed to make cars into wheels, we could have them also implementWheel—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!
If the goal is speed then just use a few turbofish.
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!
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?
Does that stand for SQL WTF?
Here’s the real question… What licenses are the wheel and door using?
I bet it uses ffmpeg…
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?
It is MIT licensed, but it’s not implemented in rust.
Clearily it must therefore be rewritten.
The wheel is Open Domain and does not belong to anyone.
“Or as I’ve recently taken to calling it, saw plus trap”
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.
You’re talking about YAML? /s
LOL. not far off
They started out with something close to YAML. As the project moved forward, they found out they needed to represent logic with interlinked sections. They needed section 3, point a to link back to section 1 point 3, sub point 2. So they toyed with some assembly-like operations. Then they needed some inheritance. They really just slowly re-implemented the common applications of xml one at a time, it just had less brackets and <> symbols when they were done.
it just had less brackets and <> symbols when they were done.
Hence making the parser more inefficient than XML?
It wasn’t without some advantage. The client hating it didn’t bode well though
The client hating it just means you’re smarter than them and should press on to help them outgrow their ignorance. It’s a good sign.
YAML definitely felt less intimidating to me than XML, when I first saw them.
But the YAML examples also had much less information in them than the XML ones.
But not having to type all those brackets definitely helps. In case of XML, I am always looking to just get a GUI going for it instead, because typing it out feels cumbersome (I’m from C++)
Re: the not-XML-instead-of-code thing. Eventually, this sort of thing turns into a programming language. It’s just like carcinisation. Or you wind up writing ever-more code to support the original design. The environment inevitably creates evolutionary pressure that only if/else and iteration logic can solve, forcing the design ever closer to being Turing-complete.
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.
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…
I’m thinking WaaS
Circular thinking
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.
The wheel doesn’t need to be reinvented, meanwhile a certain wheel is pushing for the complete removal of adblocks in its extensions.
Probably not fair to equate that piece of software as a wheel, or better yet, let’s just reinvent it with the Adblock.
The wheel of the metaphor-of-thing-as-wheel exists and is widely understood, but apparently needed to be reinvented as a metaphor involving a roughly rollable shape?
Challenge failed.
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?
I mean it sounds like you just enjoy spending your time doing that sort of thing. I’d say that was a good use of your time if you wanted to do it, no?
Im at the compose2nix phase of this pipeline. Ive got a bunch or sevices in Docker compose files and all of my systems have been running Nix for over a year now. Ive gotten the hang of my repo and made a couple modules for my specific uses and im hooked.
What would you suggest to migrate all my compose files into a nix friendly environment? I use flakes as well.
NixOS Chad
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.
That involves knowing how to read
Not necessarily.
