I guess that's fair. I use RxJS with React and other front-end libraries all the time. It and state machines via xstate (which by no coincidence has built-in support for RxJS) enables devs (especially component authors) to not depend on proprietary ways of managing state and event/data changes over time associated with Web app or component front-end libraries that don't transfer across different front-end libraries as much. Its use essentially as a push-based endofunctor abstracton (consistent way to reason and chain value changes over time) makes it typically a better way to handle async and synchronous over time (including collection of data) than promises and in many cases async iterables that yields promises. A Observable can do the things a promise can, but a promise can't do everything an Obsevable can. Observable is also now renewed to be available directly in browsers to compliment existing DOM event APIs as a better and more advanced way to handle events.

They are working on "automatic AI testing"

why ?

lol

yes! Angular 18 will come out later this week. And they announced even better performance and bundle size reduction

As someone with a more clear view from the outside I say no.

Depends on what you want to achieve at the moment. If your goal is just to learn the framework for fun/side projects/expand your view, RxJS can wait till quite a bit later. But if you goal is to become a professional frontend developer, or more specifically, Angular developer, yes, you should invest in learning RxJS. (They *will* come up in an Angular interview, if you need a more substantial reason. :) I'd suggest getting familiar with the essentials first, like data and event binding, routing, forms, DI, state management, etc. Then when you dive into the reactive style of programming, learn common RxJS operators and use cases and *unlearn* all the bad habits as you go. Async programming is difficult and tricky at the same time. RxJS is not the only tool but it does provide tools to let you deal with the async complexity more concisely. And observer pattern has been around for decades so there's nothing wrong learning about a tool that promotes and implements it. But yeah, depending on your capacity and primary goal, you should prioritize your learning wisely.

WizAng

doesnt really sound like an Angular problem to me

They need money bro to re-write!!

How is this effecting you are these your companies?😂

@@GLawSomnia Yes, it isn't an Angular issue. I didn't word it, but you understand what I mean.

@@ivan.jeremic It would not be fun not to use the latest version. However, I understand that updates cost a lot of money.

Why?

Unfortunately, static members cannot reference class type parameters. You could have: new input().required(); But I hope we can all agree that's gross and worse than input.required();

at marketing and selling themselves, true

for hobby projects, maybe.

for noobs