> I discovered sockets were both broken and deprecated.
Just in case anyone gets the wrong end of the stick, "Haskell sockets" are both working and supported (quotation marks because there is no single blessed implementation: sockets are just a (few) library(ies)). When people want help choosing a library, I point them to https://haskelliseasy.readthedocs.io/en/latest/, which is an opinionated, curated list.
Could you share a bit about your experience with sockets in haskell? I had the chance to use sockets in haskell on multiple occasions and they worked as expected.
It was a while since I was involved in that space, but at the time, you had things like the Text library to properly handle human text, ByteString to handle plain 8-bit arrays, Conduit and Pipes as two libraries to do streaming I/O (both network and file) with resource usage guarantees.
I'd love to help you with the roadblocks, but I need more specifics to do that.
Haskell needs to replace the standard prelude and burn the old documentation.
I have used dozens of languages and never really had any problems.
But the simplest of tasks in Haskell immediately put up roadblocks.
Iām sure if I had sufficient reason I could get passed these problems, but when easy things are not easy one loses interest fast.