I like how the author acknowledges the problem with the very word "type" - https://www.cs.tufts.edu/~nr/cs257/archive/stephen-kell/in-search-of-types.pdf https:

I like how the author acknowledges the problem with the very word "type" - https://www.cs.tufts.edu/~nr/cs257/archive/stephen-kell/in-search-of-types.pdf https://www.cs.tufts.edu/~nr/cs257/archive/stephen-kell/in-s... The word "Type" is such an overloaded term, just like how "Workflow" is an overloaded term in the tech industry[1]. For example, when people say "X is strongly typed language" means something much different than when people say "In Haskell, function have types" [2] or "Idris has dependent types". They aren't completely unrelated, but they mean two very different set of things depending on the context. [1] https://news.ycombinator.com/item?id=21544453 https://news.ycombinator.com/item?id=21544453 [2] http://learnyouahaskell.com/types-and-typeclasses http://learnyouahaskell.com/types-and-typeclasses