collaboration about transducers-js HOT 3 CLOSED

@jlongster thanks for opening up this issue I also think collaboration could be very fruitful and you bring up a lot of good points. I'll discuss this with team at Cognitect tomorrow and get back to you.

from transducers-js.

@jlongster I've made several changes to master to accommodate interoperability and reuse. First off, all transducer types are exported - they are a part of the public API - anyone can combine them with any other transducer implementation given that they follow https://github.com/cognitect-labs/transducers-js#the-transducer-protocol. Feedback on this simple protocol is appreciated.

It's unlikely we'll pursue all the other nice bits that are available in your implementation - and we certainly don't mean to discourage separate implementations! That said I think at 2K gzipped transducers-js is small enough to be the underpinning of any higher level functionality you may want to provide yourself. If that's not desirable then I think we can meet at a shared protocol. Happy to discuss any issues you may have with the protocol as currently described.

from transducers-js.

@swannodette Looks good to me. I'm glad you documented the protocol in the docs; our libs mostly already matched but it should be documented. The protocol looks great.

I understand not wanting to pull in my APIs; you all have your own priorities/vision. No worries, I think multiple libraries is good as long as it's not too confusing. I may add a section explaining the differences. Since our internal implementation is basically 100% the same, I'll think about building on top of your lib instead and just providing new APIs. Not sure yet.

Either way, having a standard protocol really helps with projects like js-csp. Thanks!

from transducers-js.