Merge with iter-tools? about ixjs HOT 3 CLOSED

Somehow I never saw this. Thanks for the background on the project and its maintainers! I've also been finding it difficult to summon the time and energy to do the work I've planned for iter-tools, which is one of the main reasons I'm interested in seeking out more collaboration.

I'm ashamed to admit that I don't know very much about how iter-tools perf holds up in the wild. I know it has some unique abilities in the JS ecosystem like the ability to split infinite iterables. I have made some significant steps on constant-factor performance improvements such as centralizing any code I can (so it gets hot faster) and attempting to maintain monomorphism across the library, but there are still many more ideas I want to test and implement.

from ixjs.

You might not wish to close this as completed, but rather as not planned

from ixjs.

Ix is largely a port of .NET's System.Interactive package (@mattpodwysocki was a member of the LINQ team), making it the iterable (and async-iterable) dual to RxJS.

The motivations to this point have been to maintain duality with Rx and faithfully port System.Interactive to idiomatic TS/JS, but it's definitely time to start evolving it in a more performance-oriented direction (something I greatly admire about iter-tools 🙂). Neither of us work on it full time anymore, so finding the time to do that has been difficult.

I would also say that iter-tools is packaged better -- it's at least 7 times smaller than ix while supporting (afaik) the same basic use cases.

You're probably looking at the main ix package, which bundles all the ESNEXT CJS/ESM/UMD and ES5 UMD (plus typings + sourcemaps) into one big package. This is purely for convenience, and because disk space is cheap. Because predicting everything about library consumers build toolchains is impossible, we also publish individual targets under the @reactivex/ix-* namespace for more specialized or disk-conscious consumers.

from ixjs.