News for hackers. Stuff that matters.
Re:Dynamic type systems are not inherently more open by falcolas on Sunday January 19, 2020 @11:13AM (#22092146)
Every time this comes up, I think about how the pendulum swings back and forth. For example, if we take static and dynamic type systems in a slightly larger scope, we’ve just recently moved from a static system to a dynamic system, because the static system was being mis-used by “libraries”.

I’m speaking of the recent move to deprecate user agent strings, and the pushing of “feature detection”.

It’s just human nature in the end. We’re not computer. We will never use a static spec to its full potential; we’ll break a type system wide open the moment we get to our limit of tolerance for not getting the job done.

We need type inference more. The computer has built the AST, why do compliers seem so incapable of traversing that tree and finding the type errors for us?

Re:Dynamic type systems are not inherently more open by haizan on Sunday January 19, 2020 @02:03PM (#22093185)
It seems to me that your user agent example fits better on the structural/nominal typing dichotomy, rather than static/dynamic.