Tony Morris

@samth @bitemyapp @puffnfresh @djspiewak I am compelling you to PLEASE show me where I am wrong. This is my position until such time.

@dibblego @bitemyapp @puffnfresh @djspiewak I (a) know type theory (b) regularly willingly eschew types. Types are an SE tool w/ tradeoffs.

@samth @dibblego @bitemyapp @puffnfresh @djspiewak Not goading, genuinely curious: what are some resources for learning about the tradeoffs?

@deech @dibblego @bitemyapp @puffnfresh @djspiewak Similar to tradeoff of any tool My research covers this, also see: http://www.cs.umd.edu/projects/PL/druby/ …

@samth @deech @bitemyapp @puffnfresh @djspiewak this is not a trade. Type holes do exactly the same.

@dibblego @samth @bitemyapp @puffnfresh @djspiewak -- type holes do not provide the same experience as, say, a smalltalk-80 environment.

@coreload @samth @bitemyapp @puffnfresh @djspiewak Agreed. Type holes is a far more robust experience.

@dibblego @samth @bitemyapp @puffnfresh @djspiewak -- it's a tradeoff. I don't need the extra robustness as much as I need the expressivenes