As I spend my Saturday night proving properties of the type system for an imperative programming language, my main takeaway is that imperative languages were a terrible mistake and should be banned
-
-
Replying to @geoffreylitt
I'm curious how seriously you mean this. Do you think "the ease of proving properties of the type system for X" should be a significant factor in judging X?
1 reply 0 retweets 1 like -
Replying to @qualmist
This was mainly a joke out of frustration :) I do think there's something to your question though! I think that ease of building dev tools is important to consider, and functional languages often do well on that dimension.. brain is too fried to say any more
2 replies 0 retweets 0 likes -
Replying to @geoffreylitt
1. Hot take: "ease of proving properties of the type system for X" doesn't have much to do with "ease of building dev tools for X", which in turn doesn't have much to do with "experience of programming in X, with dev tools". 2. What are your favorite Haskell dev tools?
2 replies 0 retweets 2 likes -
Replying to @qualmist @geoffreylitt
Re #2: It seems like haskell's purity should in theory allow for absolutely killer time travel reversible data-observable devtools, but somehow the incentives aren't there for one to come along
1 reply 0 retweets 1 like
Though the same goes for type-driven autocompletion wizardry and deep, intuitive refactoring tools...
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.