“…the barrel.” Apples don’t come in bunches, but at the time the saying was coined they were carted around like that. (Also it only took one, not a few.)

(I suppose the modern version is “one nazi spoils the bar.”)

And as for your specific question: typechecked code doesn’t get to production with a type error; it won’t compile. There’s a common phrase, “left-shifting errors”. It means catching bugs as early in the development cycle as possible. In terms of things like developer time (and patience), it’s far more cost-effective to do so.

I worked on OpenStack back in the day: millions of lines of untyped Python.

Let’s say you’ve got an X509 certificate. You know you can probably pull the subject out of it - how? Were I using Java (for instance), the types would guide my IDE and make the whole thing discoverable. The prevalent wisdom at the time was that the repl was your friend. “Simply” instantiate an object in the repl then poke at it a bit.

And it’s not just that kind of usability barrier. “Where is this used?” is a fantastic IDE tool for rapid code comprehension. It’s essentially impossible to answer for a large Python codebase.

Don’t get me wrong: python is still a great go-to tool for glue and handy cli tools. For large software projects, the absence of type enforcement is a major impediment to navigation, comprehension and speed of iteration.

He doesn’t want to be co-president. He’s a founder of the USA.

Fucking well said.

Sexy anti-woke task force officer?

The lizardfolk brigade.

In 2016, 96% of UKIP membership voted for (some version of) Brexit - their raison d’etre. 4% is a typical fraction of any group to be chaotically bonkers.

Thank-you.

And 51 feels prime. Someone sgould write a letter.

It’s “revelation,” singular. Like trivial pursuit.