Repository navigation
docs: add a comparison table to the README - #398
Merged
Merged
Conversation
Positions FxTS against lodash and native Array/Iterator Helpers on the axes where it differentiates - lazy evaluation, AsyncIterable pipelines, backpressure concurrency, curried composition, async early termination, and literal-preserving inference - with honest partial marks (lodash chain, lodash/fp, sync-only native helpers). Links the p-limit/p-map migration guide. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a "Why FxTS?" comparison table to the README, right after the intro bullets. It positions FxTS on the axes where it actually differentiates — lazy evaluation, AsyncIterable pipelines, backpressure concurrency (
concurrentPool), curried data-last composition, early termination across async work, and literal-preserving type inference — against lodash and native Array/Iterator Helpers (ES2025).Markings are honest: lodash gets partial credit for
_.chainlaziness andlodash/fp, native Iterator Helpers get full credit for sync lazy evaluation and partial for early termination (sync only, async helpers still a proposal). Rows where everyone ticks the box (deep utils) are included so the table doesn't read as cherry-picked.Also links the new p-limit/p-map migration guide (#397) for the concurrency row's audience.
Test plan
🤖 Generated with Claude Code