Details

Observables have been the Angular Community's reactive primitive since Angular 2 was released with a strict dependency on RxJS. However with the release of Angular version 16, a new reactive primitive has been introduced - Signals - leaving many developers wondering how this should impact their reactive workflows. Do Angular developers need multiple reactive primitives? Do developers still need RxJS? When should developers use Signals and when should they use Observables? And most critically, does the introduction of Signals necessitate refactoring an entire code base like with previous AngularJS applications?

Let’s find it out together, in this talk we will investigate what Angular developers NEED to know about switching to Signals, the differences between Observables and Signals, and provide best practices and patterns for making Angular applications more reactive today and for days to come!

Speaker: Jan-Niklas Wortmann
As a Developer Advocate for JetBrains, Jan-Niklas Wortmann isn't just another coder—he's a code evangelist. With TypeScript as his weapon of choice, he's on a mission to make your dev life easier, one line at a time. Angular geek? He's got you covered. Obsessed with reactive programming? So is he. Outside of fine-tuning the developer experience at JetBrains, Jan is a Google Developer Expert for Angular and a part of the RxJS Core Team.

0 Response to "August 21: AngularKC: Reactivity in Angular Applications: Signals vs. Observables - Jan-Niklas Wortmann"

Post a Comment

Blog Archive

Followers