Professionally and on my side projects I use Haskell. I want effect tracking. It's just you have to use monad transformers to compose stuff
-
-
Things get ugly pretty quick. Plus, stacking monad transformers ain't cheap. You end up rolling your own most of the time
2 replies 0 retweets 0 likes -
With all respect, I think you are wrong.
1 reply 0 retweets 0 likes -
Considering my stand on this is subjective. I don't mind. I'm aware I chose comfort over correctness. Scala is ugly enough.
1 reply 0 retweets 0 likes -
But your reasoning is wrong. It's not trading anything. It's throwing away, for no benefit.
1 reply 0 retweets 1 like -
Ah I see, I agree with you. But instead of pretending people will follow guidelines I rather use a language that makes it mandatory
1 reply 0 retweets 0 likes -
That's why I rather write my code in Haskell instead of having half assed effect tracking in Scala
1 reply 0 retweets 1 like -
There is a good reason to not write IO in Scala. This reason is not one of them. It's not good reasoning.
1 reply 0 retweets 1 like -
What would be the good reason to not write IO in Scala then, except the obvious performance hit ?
2 replies 0 retweets 0 likes -
Performance hit for I/O stuff is irrelevant. For CPU-bound work (IORef,MVar) Haskell might have TCO, but takes significant hit too ...
3 replies 0 retweets 0 likes
Haskell takes no performance hit for System.IO#IO. It also doesn't do TCO, because it is superior in other ways.
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.