I agree, strong typing is for weak minds. I work with a weak mind so I want strong typing.

There’s no difference in speed between typing disciplines. In point of fact, there cannot be. You must know the structure of your data to program against it. Whether you write it down explicitly or implicitly changes nothing but the location you wrote it down.

My guess is that this is really a measure of how much abuse the language will tolerate. C# probably lets you get away with a bunch of things (like checking for nulls) that F# requires.

Even that definition is myopic. The Dems only want to return to 2016 in the same way I want to return to 1933 when minimum wage was actually valuable. It’s not a focus on the past when your actions wouldn’t change even if the past wasn’t there.

It’s not the worst thing. Like any other test there are more and less valuable methods. Imo, the hardest part is not coupling yourself to the incidental. All tests have that issue but UIs are almost entirely incidental. Styles, layout, and even data and function can be incidental and thus likely to change.

So so many unit tests I see don’t meaningfully test anything. It would be faster to just read the unit under test because the test itself presents nothing that you wouldn’t instantly recognize. Or the test is so tightly coupled to some arbitrary property that of course the test fails whenever you change something. UI tests at my current place are terrible for this, as they’re just comparing DOM structures so any change breaks it.