You cry

I want a roof python now

Good luck reaching an unwilling horse’s eye balls

I also vaguely remember such a story but there the aliens got fukd up because when all hope was lost humans just started kamikaze-ing their ships. Spite is our superpower.

If you get prep time you could set up some traps.

Assuming both sides see it as a fight to the death, the horse will also engage so you could just run away into a bunch of traps. All you need is for the horse to injure a leg in one trap and it’s done for. I think even just some holes with a couple spikes would be enough to injure and maybe even sprain an ankle.

Without prep time you’re pretty doomed, I think your best bet is either climbing up a tree to buy you some prep time to make a spear out of the branches or worst case diving in, aiming to do damage to its legs (unlikely) and hope you are able to get out without being trampled (unlikely)

Dogmatic statements like this lead to bad, messy code. I’m a firm believer that you should use whatever style fits the problem most.

Although I agree most code would be better if people followed this dogma, sometimes mutability is just more clean/idiomatic/efficient/…

Is there any reason why you didn’t just switch the keyboard layout to US if that’s what you’re used to?

I switched to US at some point because many if the keys for programming were just so much easier to access. If I have to use a pc for any decent amount of time, I just switch the OS layout to US now regardless of the layout that’s printed on the keyboard.

Nope, IaaS. With a VPS you are in charge of everything except for the hardware. PaaS the only thing you’re in charge of is your code.

Dot in dutch is punt

One crate is still one item

Regarding your note on quantum secure cryptography: Yes it exists and is a thing, but a lot of the internet still relies on cryptography that is not quantum secure, e.g. TLS for starters.

Oh yeah, it’s actually pretty extensive and expressive. If you’re interested in this sort of stuff it’s worth checking out the IR language reference a bit. Apparently you can even specify the specific garbage collection strategy on a per-function basis if you want to. They do however specify the following: “Note that LLVM itself does not contain a garbage collector, this functionality is restricted to generating machine code which can interoperate with a collector provided externally” (source: https://llvm.org/docs/LangRef.html#garbage-collector-strategy-names )

If you’re interested in this stuff it’s definitely fun to work through a part of that language reference document. It’s pretty approachable. After going through the first few chapters I had some fun writing some IR manually for some toy programs.

LLVM is designed in a very modular way and the LLVM IR allows you to specify e.g. if memory management should be manual/garbage collected.

You could make a frontend (design a language) for LLVM that exposes those options through some compiler directives.

In general I’d heavily recommend looking into LLVM’s documentation.

It’s always fixable, just not always worth the effort

Reminds me of the old joke that monads are easy to understand, you just have to realize monads are just monoids in the class of endofunctors.