RxJS
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
4recommend
1warn against
Feb 8, 2026first mention
Aug 20, 2026latest mention
Why people recommend it
“RxJS is a beast to approach at first but it's a genuinely cool library”
“its a challenge to learn for those not used to the pattern but its very nice”
Show 2 more
“I also prefer the power of RxJS over signals”
“I love rxjs but I cannot recommend it without that same calibur of tooling.”
building an RxJS vite pluginon “Ask HN: What Are You Working On? (February 2026)”
Caveats and dissent
Often compared with
Who recommends it in their own words
Threads where it came up
- Angular v22 3 mentions
- There's no such thing as a small software team anymore 1 mention
- The Three Pillars of JavaScript Bloat 1 mention
- Web Components: The Framework-Free Renaissance 1 mention
- JavaScript-heavy approaches are not compatible with long-term performance goals 1 mention
- Ask HN: What Are You Working On? (February 2026) 1 mention
Data: rxjs.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 8
“the only library in there is rxjs”
“RxJS is a beast to approach at first but it's a genuinely cool library”
“its a challenge to learn for those not used to the pattern but its very nice”
“rxjs was a bad choice for data management”
“Most things in Remeda, ramda, rxjs”
“I also prefer the power of RxJS over signals”
As with most RxJS problems the diamond dependency problem can often be fixed/solved with the right combination of even more advanced operators/combinators. Often the easiest solution is `combineLatest`, but as mention that will over-fire depending on your update patterns. Sometimes a simple `throttle` is all the backpressure fix you need on that to reduce diamond over-firing, especially in combination with a cool sch
“I love rxjs but I cannot recommend it without that same calibur of tooling.”