[pie_flavor]

The standard complaint of pointless type errors that static type analysis would catch has nothing to do with weak typing, nor does the other one about unreliable listing of available ops in your editor by pressing `.` and looking at the autocomplete list. If you think the only thing people think is wrong about dynamic typing is JS `==` then you are swinging at a strawman from a decade ago.

[Pay08]

In every IDE I have ever used, the autocomplete hasn't been a problem. They at the very least tend to put the concrete type you're working with at the top of the list.

As for type errors, the strictness that static typing enforces is simply not needed in the majority of cases. And in the ones where it is needed, most languages I know provide a way for you to enforce the usage of the correct type.

[pie_flavor]

What's that supposed to mean? If I say `def foo(x)`, what autocomplete do I get off `x.`?