News for hackers. Stuff that matters.
Re:Green vs. Brown Programming Languages by mavelikara on Saturday April 24, 2021 @04:31PM (#26928061)
What were the other options available in Haskell in 1992, besides Lazy IO, which made for a great IO story then? Please point me to code or papers from then because I am genuinely interested to learn.
Re:Green vs. Brown Programming Languages by tome on Sunday April 25, 2021 @03:49AM (#26931059)
Reading and writing between handles and buffers, just like any other language. If you object specifically to the adjective "great" then, well, I don't think that was the operative point of the original comment.
Re:Green vs. Brown Programming Languages by mavelikara on Sunday April 25, 2021 @01:20PM (#26934474)
I object to both the use of “great” and the (needless, IMO) mention of Java in mrkeen’s comment.
Re:Green vs. Brown Programming Languages by mrkeen on Sunday April 25, 2021 @04:54AM (#26931317)
I might be naive, but I just assumed that I was still using lazy IO.

I've used conduits before, and understand that pipes fit the same design space.

But most of the time I just use read and write operations exposed by Bytestring, etc.

My point is that since I like IO today, and I didn't think that laziness had been removed, then I probably would have liked IO back in the day.

Re:Green vs. Brown Programming Languages by dllthomas on Tuesday April 27, 2021 @10:22PM (#26964723)
"Lazy IO" is things like `readFile :: FileName -> IO String`, where that String you get back secretly hides a thunk that will read more from the file when you evaluate it (even in pure code).

The operations provided by `Data.ByteString` do not work like this; the ByteString you get back represents a buffer, and it has already been processed by the time the RHS of >>= starts executing.

The operations provided by `Data.ByteString.Lazy`, on the other hand, do work like that; the ByteString you get back is a linked sequence of buffers, and some of those links might be thunks to go get the next bits of the ByteString for you.

This is why a Data.ByteString.ByteString and a Data.ByteString.Lazy.ByteString are different types, and you can't just pass one where the other is expected (unless you've abstracted over it) - they're actually shaped differently.