3 ms·
> this is harder to read than the callback approach right now Why do you think this is (I'm asking honestly, not trying to be snarky). Is it because you are no
by treerex 13y ago
> this is harder to read than the callback approach right now
Why do you think this is (I'm asking honestly, not trying to be snarky). Is it because you are not familiar with reading Lisp? The notation used to access channels is confusing? Unfamiliarity with the go-block concept?
It took me a while to fully internalize the combination of syntax and power of go blocks, but now that I have reading core.async code (I have not yet had a need to actually use them, and no time to port an existing codebase) is much easier.
I question whether the statement that callbacks are easier to read and understand is merely due to being accustomed to them. Core.async represents a radical departure from existing designs, and that can be jarring. Does this mean better syntactic sugar won't be created as developers gain experience? Or course not.
- krosaen 13y agoYeah, I think it's just unfamiliarity with this approach + deep familiarity with the callback approach, and I'm merely reporting my experience and not making a judgement on the approach in general. Sometimes when I see a callback it's a helpful signal that something asynchronous is happening - it's good to know. That said, with some further accustoming to the channel approach, it will probably both read naturally and be apparent where the async stuff is happening.