Re:Clojure will affect the way you think about programming
by KirinDave on Friday August 04, 2017 @02:07PM
(#14930617)
I dunno. Except for one very specific project, I've yet to see a "Wow!" use case for transducers. The only place where they really shine is working with channels, but I think channels are a big design mistake (after extensive work trying to tame them).
[ Parent
| on HN ]
Re:Clojure will affect the way you think about programming
by arximboldi on Friday August 04, 2017 @02:44PM
(#14930925)
Interesting! Why do you think they are a big design mistake? I can understand how they can be misused, but I find myself missing them in every language I used that doesn't have them...
Re:Clojure will affect the way you think about programming
by KirinDave on Friday August 04, 2017 @06:16PM
(#14932824)
So either I'd rather talk about the COMPUTATION and resource safety rather than the channel, as in Pipes/Conduit/Streaming from haskell.
OR, I'd rather deal with a direct actor model a la Erlang, Pony and Cloud Haskell.
Go's experience is so goddamn miserable it should just put the entire notion of async channels as a higher level programming library to bed. As a low-level primitive, it's okay but not fundamental.