Docility. Don't forget the docility genes.

Punxsutawney Phil saw a tiny cloud in the distance, so they chickened out of launching.

That summary at the top of this story is just way too long. I'll have a chatbot break it down and give me the gist.

By that standard they could make any law including one requiring everyone to pay $1,000,000 for breathing air.

I'd worry more about the risk from random mutation than targeted changes.

No flying cars, no vacations to the moon, no energy too cheap to meter. But god damn, at least we'll have superheroes running (or flying) around and delivering public service messages.

This is their second attempt.

I feel like Blue Origin wasted money on an expensive hard to build rocket.

Why is that wasted money? Because its main competitor SpaceX thinks VERY HARD about manufacturability. Compare the speed at which SpaceX hauls out new Starships and Raptor engines. The USA used to know that manufacturability was important. That's how WW2 was won. One example, the Opel Blitz truck built by the Germans versus the GMC CCKW (nicknamed "deuce and a half"). The problem with the Opel Blitz was that it was hard to manufacture, hard to maintain. The GMC CCKW had "simpler" design that was easy to manufacture and easy to repair. The bolts were all the same sizes, interchangeable, and things like that. While Germany struggled to build 27,000 trucks in 1943, America produced over 560,000 GMC trucks alone. Reference: https://www.youtube.com/watch?...

If you're locked inside an ATM, have you tried banging on the case to alert passers by?

Almost nobody uses "untyped languages". Few of those even exist, with Forth and various assembly languages being the main examples. (C, with its type system that is as airtight as a sieve, gets an honorary mention.)

You're probably harping about dynamically typed languages. In such languages, the runtime still knows *exactly* what type every item of data has. These are not weakly typed. But what you obviously prefer are "statically typed" languages.

Static typing might statistically reduce some errors, but it certainly can't "eliminate whole classes". Consider "set_warhead_target(float latitude, float longitude)". Did the type system give you any protection from accidentally swapping the two parameters? That's really the problem that you're so worried about: accidentally using the wrong data value in the wrong place.

However, very few statically typed languages (with Rust being a notable exception) have eliminated the biggest source of type errors in computing: Null, which is a bogus placeholder that matches any pointer type (or reference type, depending on the language's nomenclature). So in many cases you have no less risk with static typing than you do with accidentally feeding a string into a Python sqrt() function. And in the case of C or C++, you can be much worse off, as in segfaults and remote exploits.

Humans didn't die until the 21st century?

[X] Irrational paranoia about the above

You do realize your butt isnâ(TM)t supposed to be in the toilet water, right? Thereâ(TM)s a reason the toilet seat exists, use it!

Theft is when someone takes something from you without mutual agreement (force) or without your knowledge.

Are both parties aware? Your post is false equivalency. Flight attendants for example only get paid for the time for when the airplane doors close until landing. They don't get paid for the fixed time spent traversing through the airport. They don't get paid for any pre-flight task such as prepping the cabin or boardingin passengers. Both parties are aware of those employment conditions and agreed to it. It's vastly different than "theft" which occurs without full disclosure.