5 ms·

I think Typescript can sometime have a mind of its own, but it's certainly an enrichment and with Rx everything just falls into place. At this point it's hard

I think Typescript can sometime have a mind of its own, but it's certainly an enrichment and with Rx everything just falls into place. At this point it's hard to ignore that all the UI libraries are just paradigms and patterns, and how we use them is getting less important. These days I just want to write Component-style UI code, and I'll be fine. Similarl things can be said about RxJS, but I think since it's a different level of abstraction, it will hit much harder, once it gains more traction. And it's already building up a solid community much faster than before. the only thing standing in the way of people learning RxJS is the same as Angular / Vue / React. It's scary and there's a lot of fatigue still. I hope that this year is thus going to be even better for teaching. ^^ Tldr; RxJS is going to be huge, if we can teach it more and JS fatigue calms down.

robwormald 10y ago
We've got some really cool ideas to make Rx really first class in Angular. It's already pretty deeply integrated, but with a little work, it'll be awesome.
- philplckthun 10y ago
  definitely agreed! It's become one of the biggest "advocators", so to speak. But I think people will want to learn it as a default, async primitive in JS as promises now are. Not saying support from Angular and other projects and also companies doesn't help, since it makes it look less like a "scary, new thing", but I think more people should start to teach it's benefits to be frank and blunt about it ;)
  - robwormald 10y ago
    absolutely. we're 100% invested in Rx, and more than anything else I'd like to see the Observable type standardized.
- cormacrelf 10y ago
  What are they? I've been developing with the @ngrx suite, and it's been mostly pretty smooth, what more do you want? I would like to see a piece of documentation that lays out explicitly what happens when you pass around Observables. Hot ones, cold ones, when the auto-unsubscribe clicks in, whether this.property$ = some_observable(); this.property$.subscribe(fn); ... will auto-unsubscribe (does it? who knows... try it?), what happens when you async pipe and its interaction with ChangeDetection...

robwormald 10y ago

We've got some really cool ideas to make Rx really first class in Angular. It's already pretty deeply integrated, but with a little work, it'll be awesome.

philplckthun 10y ago
definitely agreed! It's become one of the biggest "advocators", so to speak. But I think people will want to learn it as a default, async primitive in JS as promises now are. Not saying support from Angular and other projects and also companies doesn't help, since it makes it look less like a "scary, new thing", but I think more people should start to teach it's benefits to be frank and blunt about it ;)
- robwormald 10y ago
  absolutely. we're 100% invested in Rx, and more than anything else I'd like to see the Observable type standardized.
cormacrelf 10y ago
What are they? I've been developing with the @ngrx suite, and it's been mostly pretty smooth, what more do you want? I would like to see a piece of documentation that lays out explicitly what happens when you pass around Observables. Hot ones, cold ones, when the auto-unsubscribe clicks in, whether this.property$ = some_observable(); this.property$.subscribe(fn); ... will auto-unsubscribe (does it? who knows... try it?), what happens when you async pipe and its interaction with ChangeDetection...