There might be other kinds of damage where the quicker altitude gain of a normal rotation is crucial for survival.
I'm skeptical whether pilots can realistically make this kind of decision, given that they have no more than a few seconds to make it, and in cases such as this based on very incomplete information about the state of their aircraft.
The Morris worm is certainly the more historically important one but AFAIK nothing has ever beaten SQL Slammer (2003) for sheer sleekness and propagation speed: 376 bytes, sent as UDP packets to randomly generated IP addresses as fast as the network interface could pump them out. Infected all susceptible hosts on the entire Internet within 10 minutes. Thankfully, that was only MSSQL servers and, being that sleek, it had no persistence mechanism. So turning the machine off and on again removed the infection completely.
That's usually with skills that few have the time to acquire. But I also saw on LPL where he tested a cheap Chinese lock, where the "hardened steel" had a visible groove after just a few strokes of a file, and you could use pliers to rip off the plastic cover around the keyhole, after which all the little parts of the lock mechanism came tumbling out...
> To their great dismay, the engineer in Australia could not open the safe because the combination was stored in the now-offline password manager.
Classic.
In my first job I worked on ATM software, and we had a big basement room full of ATMs for test purposes. The part the money is stored in is a modified safe, usually with a traditional dial lock. On the inside of one of them I saw the instructions on how to change the combination. The final instruction was: "Write down the combination and store it safely", then printed in bold: "Not inside the safe!"
Yes. I once overheard a flat earther argue that spare reporting is fake because there are supposed to be tens of thousands of satellites, yet photos from the ISS don't show any of them.
Those large red blobs are not visualizations of debris fields. You can toggle them off as "instruments", and debris is actually toggled off by default.
I strongly suspect the post was a joke, perhaps deliberately mangled by machine-translating it not just once but multiple times between different languages.
Note that in the original thread, there was someone who requested (in Japanese) to repeat the question in Japanese, and was ignored.
Trying to reverse engineer the translation errors when you know zero Japanese is absurd.
I'm only semi-fluent in Japanese, but none of it makes sense to me. "Runtime" (in the computing-related sense) in Japanese is 実行時, or one might use the English word tansliterated to Kana, ランタイム, but there is absolutely no connection from either of those to goats.
I think there's a chance you're correct, but my gpt translation^ has him saying "please email me directly"
^
Hello, Mr. Matsumoto. This is Nate.
Google Translate is incompetent and vulgar. (LOL) Please email me directly.
You can write in Japanese. I intend to help you.
See you,
In katakana you lengthen the "e" sound with a dash-like character, but in hiragana you lengthen it with an "i" character, and most romanization schemes follow the hiragana and write the long e sound as ei.