RxJS VS redux

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

RxJS is used for events and asynchronous tasks

Data flowing like a melody? Master RxJS, the reactive JavaScript library, to handle asynchronous data flows with grace and ease. Streamlined data, happy code.

> This proposal makes the same mistake as various stream implementations (including RxJS in the past) of making operators methods on the observable.

I don't think they are making a mistake. I am sure Ben knows what he is doing, given how it was he who refactored rxjs 5 with all operators being methods on the Observable, to rxjs 6 with pipeable operators.

But, their objective is not to bring rxjs into the browser, but rather to bring the Observable primitive into the browser. And, like Array prototype, which has methods, Observable, in order to be even minimally useful, needs some methods, which they modelled from TC39 iterators, for the sake of consistency.

They say:

> We expect userland libraries to provide more niche operators that integrate with the Observable API central to this proposal, potentially shipping natively if they get enough momentum to graduate to the platform. But for this initial proposal, we'd like to restrict the set of operators to those that follow the precedent stated above, similar to how web platform APIs that are declared Setlike and Maplike have native properties inspired by TC39's Map and Set objects. Therefore we'd consider most discussion of expanding this set as out-of-scope for the initial proposal, suitable for discussion in an appendix. Any long tail of operators could conceivably follow along if there is support for the native Observable API presented in this explainer.

As to

> We really need a `pipe` operator, at minimum

Maybe we don't. Note that in RxJS version 8, they have introduced a new way of piping observables, which is the rx function [0]. Maybe they are thinking of something similar for the browser. Or maybe they are thinking of using the native pipeline operator if it ever gets approved.

In the meantime, for any complex manipulations on observables, users will probably still import relevant functions from libraries.

0 - https://github.com/ReactiveX/rxjs/issues/7203

Hello and welcome! It's fantastic that you're looking to broaden your expertise in front-end development. Transitioning from Flutter to React and Angular is a great move, as it will provide you with a well-rounded skill set. ### Resources for Learning React: 1. **Official Documentation:** Start with the [official React documentation](https://reactjs.org/). It's well-written and comprehensive. 2. **React Fundamentals Courses:** Platforms like [freeCodeCamp](https://www.freecodecamp.org/) and [Codecademy](https://www.codecademy.com/) offer free React courses. 3. **React Hooks:** Understand the concept of hooks, a powerful feature in React. The [React Hooks documentation](https://reactjs.org/docs/hooks-intro.html) is a great resource. 4. **Project-Based Learning:** Build small projects to apply your knowledge. You can find ideas on platforms like [GitHub](https://github.com/) or [CodePen](https://codepen.io/). 5. **React Router:** Learn how to handle navigation in React using [React Router](https://reactrouter.com/). ### Resources for Learning Angular: 1. **Official Documentation:** Similar to React, start with the [official Angular documentation](https://angular.io/). 2. **Angular Tour of Heroes:** This is a hands-on tutorial provided in the Angular documentation. It's an excellent resource for getting started. 3. **Angular University:** [Angular University](https://angular-university.io/) offers comprehensive courses on Angular. 4. **RxJS:** Learn about reactive programming using RxJS, which is heavily used in Angular. You can find resources on the [official RxJS documentation](https://rxjs.dev/). 5. **Build Real-World Apps:** Build practical applications to solidify your understanding. The more you code, the better you'll become. ### Making a Mark in the Open-Source Front-End Space: 1. **GitHub Contributions:** Contribute to existing open-source projects. This not only helps you learn but also establishes your presence in the community. 2. **Create Your Projects:** Start small with your open-source projects. Share them on GitHub, and seek feedback from the community. 3. **Participate in Hackathons:** Join online hackathons or coding challenges. They're great for learning and networking. 4. **Follow Blogs and Newsletters:** Stay updated with the latest trends and best practices in the front-end world. Subscribe to newsletters like [JavaScript Weekly](https://javascriptweekly.com/) or [React Status](https://react.statuscode.com/). 5. **Join Forums and Communities:** Engage with developers on platforms like [Stack Overflow](https://stackoverflow.com/) or specialized forums for React and Angular. Remember, the key is consistent practice and learning by doing. Good luck on your journey, and feel free to reach out if you have more questions! 🚀

Signal Store helps to streamline your usage of RxJS and Signals: e.g. connect and rxEffect understand both Signals and Observables

Our bus event is really simple in fact. We have declared into the core module (provided in all the application) an rxjs Subject.

Web scraping may seem like a simple task, but there are many challenges to overcome. In this blog, we will dive into how to scrape LinkedIn to extract job listings. To do this, we will use Puppeteer and RxJS. The goal is to achieve web scraping in a declarative, modular, and scalable manner.

Redux

redux - Redux is a key tool used in managing state across an application. This can be used with any web technology including React, Vue and Angular docs

Redux is a client-state library.

react-redux: A powerhouse for efficient state management and data flow control. Learn more

Reducer-based: requires dispatching actions to update a big centralised state, often called a “single source of truth”. In this group, we have Redux and Zustand.

I am _thrilled_ to announce that:

Redux Toolkit 2.0 is LIVE!!!

- https://github.com/reduxjs/redux-toolkit/releases/tag/v2.0.0

This major version has new features, faster perf, smaller bundle size, and removes deprecated options.

It's accompanied by majors for all our Redux family packages

## RTK 2.0:

- a new `combineSlices` method for lazy-loading reducers - Updates to `createSlice` to include a `selectors` field and allow defining thunks inside

- Immer 10 w/ faster updates

- Removal of deprecated options

See the migration guide:

- https://redux.js.org/usage/migrations/migrating-rtk-2

All of the Redux libraries now have modernized packaging with full ESM/CJS compat. They also ship modern JS (no transpiling for IE11), which means smaller bundle sizes.

We've also done byte-shaving work to shrink the bundles (extracting error messages, de-duping imports)

## Redux core 5.0:

- The TS conversion we did in 2019!

- Action types _must_ be strings

- `UnknownAction` as the default action type

- Better preloaded state types

- Internal subscription improvements

- Still marks `createStore` as deprecated!

- https://github.com/reduxjs/redux/releases/tag/v5.0.0

## React-Redux 9.0:

- *Now requires React 18 and RTK 2.0 / Redux 5.0*

DEV is a Rails monolith, which uses Preact in the front-end using islands architecture. The reason why I mention all this is that it's not a full-stack JavaScript application, and there is no state management library like Redux or Zustand in use. The data store, for the most part on the front end, is all data attributes.

Oh hey, that's my post!

(yes I spend too much time refreshing HN :) )

FWIW I did end up with a packaging combination that seems to work sufficiently. I never did fix the "FalseCJS" issue that `are-the-types-wrong` is detecting. I played with double-emitting TS typedefs, and the `tsup` tool _does_ actually have support for that now (added by Andrew Branch from the TS team). So it might be more feasible now. But ultimately I decided I was tired of messing with packaging setup and that what I've got is good enough. (hopefully)

We're actually about to launch Redux Toolkit 2.0 and Redux 5.0 this week, assuming the last couple pieces come together. Here's the latest RCs - you can see the current `package.json` files in there:

- https://github.com/reduxjs/redux-toolkit/releases/tag/v2.0.0...

- https://github.com/reduxjs/redux/releases/tag/v5.0.0-rc.1