Wondering what is the idea behind naming it core.async when it seems to be more accurately described by core.csp
Async is just async, and is very confusing name for a library that implements the CSP pattern since you can have many async patterns but they are not CSP and to use the broad term "async" can be confusing. Before i read about core.async i thought that it implemented all async patterns under the sun and was deserving of such broad categorization, but it does CSP in a robust and full manner that's about it. Also, for users of async.js the name could be doubly confusing. Please educate me on the choice for naming it core.async rather than core.csp I'm still playing with it but so far (that is since this morning when i finally had the urge) it seems like a CSP based pattern and that is all. Not the swiss army knife for all async operations, or is it and I just can't see yet? Thanks, Marc Sent from my iPhone -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
