Hear! Hear!

viva la revolucion

😂

strong opinions... negatively?

negatively, but about the aesthetics of the syntax rather than anything functional i think...

and the lux syntax certainly looks very different to other lisps

:) It's been too many years since I last looked at lux to remember much about what I thought about it

prediction: at least one person prefers manifold streams

lol, i have my issues with both core.async and manifold, although i've used manifold a lot more heavily

we're considering using callbacks for an internal API as it will probably be sufficient and simpler, but core.async is also being considered

i think core.async makes for a poor promise abstraction, but is good for co-ordinating streams of things

for an API call returning a single result a promise is a better fit i think

for an API returning streams of things (like a websocket) then core.async is a good fit

i prefer the promise for the API because [1] promises compose easily and [2] error-handling is built in and also composes well

core async's killer feature is backpressure If you need backpressure then its a good choice If not, then it isnt

er, or if you are using cljs in a browser, thats a killer feature too (might be out of date on that one)

for cljs api calls from a browser i'd go with promises over core.async too - funcool/promesa wraps them nicely

but for websocket messages and streams of events in the browser - core.async is a good fit there

also if you do have a thing that core.async does work well with, combining abstractions like transducers etc is a breeze

imo a little easier to handle lotsa stuff using that (like you say w/ the example of a stream) vs promises/promise chains

unless you get deep into craig's world of streams & monads