I believe this should be rxjs. It's composable: have a stream or streams create new derived streams easily. It's lazy: you can describe what to do with data before it's available. Handling state for the multi step or async operations (loading state, cancelling requests, retrying operations) is a breeze. "Wire" your application with rxjs and you'll never have trouble modelling state with it. Typescript-friendly. It allows be both sync access to the value (BehaviourSubject) and async (Observable). I work with it closely last year and there was no situation I could not model with rxjs.
But people will stick to whatever is hyped by well-known-internet-company. Marketing wins, not quality.
I believe this should be rxjs. It's composable: have a stream or streams create new derived streams easily. It's lazy: you can describe what to do with data before it's available. Handling state for the multi step or async operations (loading state, cancelling requests, retrying operations) is a breeze. "Wire" your application with rxjs and you'll never have trouble modelling state with it. Typescript-friendly. It allows be both sync access to the value (BehaviourSubject) and async (Observable). I work with it closely last year and there was no situation I could not model with rxjs.
But people will stick to whatever is hyped by well-known-internet-company. Marketing wins, not quality.