GIT the Princess
-
You have rust:
You spent a lot of time planning and simulating the perfect rescue plan, and perform a blazingly fast
and perfect rescue,But you bore the princess to death explaining why she should stop being a princess and instead become a knight that rescue princesses.
I love rust btw, but the cultist behaviour needs to stop.
You also don't have armor, a sword, or a horse but there are crates you can use to get them! It's important that the standard library not contain tools 90% of knights will require because writing and mainting tools is difficult so we should stick to the tried and true method of relying on some random guy in Nebraska to do it for us!
-
It might not be what you expected, but lisp did it
So did PHP
-
Once again, C reigns King!
Or at least the only one left standing...
I wanna see a Python version. No wait, I probably don't:-P.
-
You also don't have armor, a sword, or a horse but there are crates you can use to get them! It's important that the standard library not contain tools 90% of knights will require because writing and mainting tools is difficult so we should stick to the tried and true method of relying on some random guy in Nebraska to do it for us!
To be fair, the random guy in Nebraska is often part of the Rust core team. Like, it's distributed as a separate library, allowing the library to make changes independently from the stdlib and to be replaced, if a better library emerges, but that doesn't mean it's necessarily of worse quality.
Having said that, yes, for some things you can't find a library by someone from the Rust team and especially for newbies, it's difficult to know which libraries are good and which not.
-
The princess is neither Sync nor Send.
And the princess doesn't live long enough to be returned from the castle
-
And the princess doesn't live long enough to be returned from the castle
But you can always get a deep copy of the princess, no?
-
Or at least the only one left standing...
I wanna see a Python version. No wait, I probably don't:-P.
wrote last edited by [email protected]left standing…
Look closely, not standing.
Being crushed underneath the overflow.
Those that were left standing, however:
- JavaScript: standing, staring at the ruins, contemplating Docker
- C#: standing in line, probably hungry after not seeing a payday despite having paid the electricity bill for running Visual Studio for hours, on top of Windows license
- Java: The horse is standing
- Lisp: The creature generated from the 3 combined may be considered as "standing"
- Go: Everyone seems able to stand on their own. I don't see a problem
- Pascal: At least the princess is still standing. Maybe not for long though.
-
Expected
git, got multiple programming languages. Nice.wrote last edited by [email protected]git clone git@⏻_toggl:Goon%20Squad/CastleWithPrincess.git cd CastleWithPrincess git log git diff add-captured-princess^ add-captured_princess > ~/.cache/captured_princess_import.diff git reset --hard add-captured-princess^ git push --force cd ~/Documents/prince-home/ git clone git@kingdom:Prince/MyHome.git cd MyHome git apply ~/.cache/captured_princess_import.diff git commit -a -S -m "Your Majesty, the princess is now in your grace." git push systemctl start wait-for-munneys -
You have rust:
You spent a lot of time planning and simulating the perfect rescue plan, and perform a blazingly fast
and perfect rescue,But you bore the princess to death explaining why she should stop being a princess and instead become a knight that rescue princesses.
I love rust btw, but the cultist behaviour needs to stop.
i dont even use rust and i hear more people complaining about rust than i hear rust users.
-
Once again, C reigns King!
I am not sure that is supposed to be the takeaway message, but sure, whatever makes you happy.
-
another one from the archives
Wait till you have to do it in brainfuck or whitespace
-
another one from the archives
Reminder that "git" is not an acronym, so there's no need to put it in all-caps unless you're YELLING (which you might be).
-
left standing…
Look closely, not standing.
Being crushed underneath the overflow.
Those that were left standing, however:
- JavaScript: standing, staring at the ruins, contemplating Docker
- C#: standing in line, probably hungry after not seeing a payday despite having paid the electricity bill for running Visual Studio for hours, on top of Windows license
- Java: The horse is standing
- Lisp: The creature generated from the 3 combined may be considered as "standing"
- Go: Everyone seems able to stand on their own. I don't see a problem
- Pascal: At least the princess is still standing. Maybe not for long though.
Joke answer: git guud
Real shit: damn that's sooo true!
Also, the Princess in the Go panel is all the way from another castle! (Java's)
-
But you can always get a deep copy of the princess, no?
Only if the crate she comes from has her properly exposed
-
Only if the crate she comes from has her properly exposed
Oh that might be the difficult part.
