- cross-posted to:
- programmer_humor@programming.dev
- cross-posted to:
- programmer_humor@programming.dev
cross-posted from: https://lemmy.zip/post/15495372
You must log in or register to comment.
You eventually would run out of Rust developers
They’re recycled, look at the end of the dev duct.
Rrally should have the two trapdoors meet into a common tunnel before hitting the turbine. As is, you could easily jam the machine if two Rust programers fall in the doors at the same time
Even the joke has mulithreading problems.
Using Rust would have prevented this race condition
As a Rust programmer, I approve this message. Tumbling through a turbine repeatedly would be less stressful than working on a large python/js codebase.
I’m a Linux System Engineer and was the only one in my team that knew Go. I decided to update our mess of old shell scripts for post-provisioning and my boss suggested that I do it in Python so it can easily by edited/fixed by anyone on the team. I spent like two days attempting to do it in Python and then gave up because it would mean transferring a bunch of source code around, installing dependencies and just general annoyances.
In the end the Go project ended up being about 1300 lines of code across a few source files, but it could act as both the client and server (necessary for our hosts in our DMZ to hit our AWX server) with a single binary and no additional dependencies. It was also only like 10 MB.
Plus you have plenty of time to tumble once or twice while your large codebase compiles.
Turbine should connect to loudspeaker to make this a closer system lol
Still means it’s not Black Start capable if the sun is not out.
