LANGUAGES Signal 124
Author argues the question about missing types rests on false assumptions about type systems
↗
The article contends that dynamic languages can provide safety and refactoring confidence through schema validation and REPL-driven workflows, challenging the perceived need for static types.
It shows that the safety versus convenience tradeoff often cited for type systems is not as clear-cut as many assume. Engineers can therefore evaluate language choices based on actual tooling and cultural practices rather than on a presumed type-system advantage.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
Schema tools such as Malli or Spec can enforce contracts at component boundaries, offering a dynamic alternative to static type checking.
Refactoring confidence in Clojure comes from editor tooling like Cursive, Calva, and clj-kondo combined with a culture of additive change rather than compiler-driven checks.
While mainstream typed languages provide some guarantees, features like TypeScript’s any, Go’s interface{}, and Java’s null and erased generics limit their practical safety compared with rigorous systems like Haskell or Idris.
THE CLUSTER