had to think a bit to remember that in the world of subtype polymorphism, when you say "X is a Y" you're not saying Y completely describes X
-
Show this thread
-
Great thing about a type: Even if it may require documentation to really *understand* it, I know the definition I see is *complete*
1 reply 1 retweet 13 likesShow this thread -
Sure the Python has pages of documentation, but in part they're more hindrance than help ...
1 reply 0 retweets 5 likesShow this thread -
... because you have to read the entire thing to uncover any hidden features that are going to jump out and fuck with shit
1 reply 0 retweets 6 likesShow this thread -
for example, sometimes there is a thin layer of film between the layers of the onionpic.twitter.com/o4VYQty7rO
2 replies 1 retweet 9 likesShow this thread -
sure we partly-describe objects in both cultures, but python objects are so complex you rarely can describe their whole nature in a sentence
1 reply 0 retweets 7 likesShow this thread -
"types are all the documentation you need" is the other shitty end of the spectrum from python
1 reply 2 retweets 12 likesShow this thread -
But you can fix the Haskell by adding docs; you can't fix the Python.
3 replies 1 retweet 15 likesShow this thread -
Replying to @chris__martin
You can. We are. By writing haskell. https://github.com/qfpl/hpython
1 reply 0 retweets 2 likes -
Only the code, at this time.
-
-
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.