François CholletVerified account

Good interface design is interactive. Programming expects users to describe *exactly* what they want, w/o interactively requesting more info

This is bad. We need code editors/languages that will comment on likely gaps between what was *actually* specified and what was *meant*

Strongly typed languages help so much to close this gap, yet so many people refuse to use them.

They are the opposite of what he is asking, hehe. He expects things that can infer what was meant, not things that require even more details

Type inference infers what was meant...

...and IDEs interactively ask for more info when inference fails.

All to specify more details, that dynamic languages just don't require. He wants to specify *less*, not tools to ease the specification.

Type inference doesn't require specifying anything and automatically prevents unintended errors. That's more inference of intent & less work