> In order to be pure it has "stop the world and record it" with monads to do any IO. That's not how IO in Haskell works, you're basically describing what Haskell would be if it literally had no side-effects ever.
I would be interesting in learning more about the "easy to reason about the complexity" part of OCaml. The problem I'm having with Haskell isn't that it's too slow, but that it's so high-level and gets so aggressively…
> Are you saying you would like to return to the languages with explicit memory management? Not really, but that does seem to be the logical conclusion at the end of the day. Haskell makes a really good case for the use…
"My perspective on this is that lazy be default made sticking to purity much more compelling as if you just dropped print statements in you weren't sure exactly when they get evaluated." And that's basically a death…
Have you tried Stack yet?
> In order to be pure it has "stop the world and record it" with monads to do any IO. That's not how IO in Haskell works, you're basically describing what Haskell would be if it literally had no side-effects ever.
I would be interesting in learning more about the "easy to reason about the complexity" part of OCaml. The problem I'm having with Haskell isn't that it's too slow, but that it's so high-level and gets so aggressively…
> Are you saying you would like to return to the languages with explicit memory management? Not really, but that does seem to be the logical conclusion at the end of the day. Haskell makes a really good case for the use…
"My perspective on this is that lazy be default made sticking to purity much more compelling as if you just dropped print statements in you weren't sure exactly when they get evaluated." And that's basically a death…
Have you tried Stack yet?