RxJS VS fp-ts

Any continuous stream of data can be declared as an observable and the user can subscribe to it and monitor the changes in the data that is subscribed to. In simple terms we can say that observable is something that we can observe the changes constantly and in real time.

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.

I think it’s great that functional programming is making its way into traditional imperative languages - even JavaScript (I recently came across https://gcanti.github.io/fp-ts/ as a pretty extreme example)

Elixir/Erlang has function-level pattern matching, which I really like. I’ve yet to see it anywhere else, though my understanding is it came from Prolog.

While I certainly agree, I've found that this is often an indication of too-complex an architecture, and a fundamental re-think being necessary. I've had projects that depend on [fp-ts], which end up incredibly generic-heavy, but still make it entirely through a typecheck(not build- typescript's just worse at that than other tools like esbuild) in seconds-at-worse.

Obviously depends on your organization/project/application, but I do like these things as complexity-smells.

[fp-ts]: https://gcanti.github.io/fp-ts/

Unlike more comprehensive functional libraries like fp-ts, each module can be imported and resolved separately. If you just need options, simply add the option module and you're good to go.

While it's quite abstract, I believe it may be useful to those of you who is interested to learn more about functional programming [in Typescript] and also get more intuition on diverse programming ideas. I use fp-ts as a functional programming library there.

The library for TypeScript that this is influenced by is here:

https://github.com/gcanti/fp-ts

Interesting how both languages with this library converge to a similar syntax, due to heavy use of functions.

Learn something that pays the bill first - nowadays it's Golang/Rust react/typescript. Then you can try some pure fp libs like fp-ts and fp-core.rs, and look through existing scala cats docs. If you'll feel bad about it - that's totally fine and expectable, fp takes a paradigm shift and not that many dev able to shift their brains way of thought due to basic psychological rigidity) (inability to change habits and to modify concepts/attitudes once developed). And that's purely a staffing and management issue - folks hired randoms out of the blue, and called 'em a team.

fp-ts, a library that caters to functional programming in TypeScript, comes with some micro-abstractions that already solve a few of our needs.

Also, don't underestimate how powerful TypeScript can be in capable hands (namely Giulio Canti's). Check out fp-ts, for instance.

You are able to type it using function overloads, an example can be found here - link, line 236.

looks like more ergonomic/focused version of fp-ts[1]

[1] https://gcanti.github.io/fp-ts/