The smallest type change make entire APIs incompatible, hence a lot of pain in OCaml: forced upgrades, forced downgrades, crazy version update schedules, extra forks, reluctance to fix bad early choices that would break compatibility, etc. Types DIRECTLY cause library badness.
-
-
The more ridiculous are those who can't not see all the badness of their "ecosystem", yet refuse to acknowledge the relationship between this badness and design decisions in their language. In the typed FP world, at least Haskell or Scala have coping mechanisms, unlike OCaml.
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I feel you're unjustly blaming types. API fragility is a real problem that should be considered carefully in PL design. But static types are not the primary cause for it, nor are dynamic types the solution. Reflection may help, but is on an independent design axis from types.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Read my blog!