@dibblego @puffnfresh @getify @davetchepak @djspiewak nobody that really *knows* anything about types willingly eschews them.
-
-
Replying to @bitemyapp
@bitemyapp@dibblego@puffnfresh@getify@davetchepak@djspiewak This statement is simply false.2 replies 0 retweets 4 likes -
Replying to @samth1 reply 1 retweet 0 likes
-
Replying to @bitemyapp
@bitemyapp@dibblego@puffnfresh@djspiewak (a) that comic is an admission that your claim is false (b) the claim in the comic is also false1 reply 1 retweet 2 likes -
Replying to @samth
@samth@bitemyapp@puffnfresh@djspiewak demonstrate it to be false, because otherwise it is a well understood expedience of many.2 replies 0 retweets 0 likes -
Replying to @dibblego
@dibblego@bitemyapp@puffnfresh@djspiewak Telling your interlocutors that they don't themselves exist is unlikely to be persuasive.1 reply 1 retweet 1 like -
Replying to @samth
@samth@bitemyapp@puffnfresh@djspiewak I am compelling you to PLEASE show me where I am wrong. This is my position until such time.2 replies 0 retweets 0 likes -
Replying to @dibblego
@dibblego@bitemyapp@puffnfresh@djspiewak I (a) know type theory (b) regularly willingly eschew types. Types are an SE tool w/ tradeoffs.3 replies 4 retweets 11 likes -
Replying to @samth
@samth@dibblego@bitemyapp@puffnfresh@djspiewak Not goading, genuinely curious: what are some resources for learning about the tradeoffs?2 replies 0 retweets 0 likes -
Replying to @deech
@deech@samth@dibblego@puffnfresh@djspiewak trade-offs generally involve the papers leading up to Haskell's type system, pre-typeclasses.1 reply 0 retweets 0 likes
@bitemyapp @deech @samth @puffnfresh @djspiewak trades often hit limitations of imagination, not type system. This is the real protest.
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.