2021-10-14
1477
#rxjs#typescript
Emmanuel John
70910
Oct 14, 2021 ⋅ 5 min read

Using RxJS Observables to transform data in TypeScript

Emmanuel John I'm a full-stack software developer, mentor, and writer. I am an open source enthusiast. In my spare time, I enjoy watching sci-fi movies and cheering for Arsenal FC.

Recent posts:

Task Scheduling and cron Jobs in Node Using node-cron

Scheduling tasks in Node.js using node-cron

From basic syntax and advanced techniques to practical applications and error handling, here’s how to use node-cron.

Godwin Ekuma
Nov 12, 2024 ⋅ 7 min read
Working With The Angular Tree: Flat Vs Nested Trees And More

Working with the Angular tree

The Angular tree view can be hard to get right, but once you understand it, it can be quite a powerful visual representation.

Lewis Cianci
Nov 12, 2024 ⋅ 21 min read
Relay logo with an orange circuit-like path on a blue background, representing the Relay GraphQL client. The article covers building real-time applications in Relay 17, including features like optimistic UI updates, GraphQL subscriptions, and Relay Resolvers.

Building a real-time application with Relay 17

Build a fast, real-time app with Relay 17 to leverage features like optimistic UI updates, GraphQL subscriptions, and seamless data syncing.

Alec Brunelle
Nov 12, 2024 ⋅ 9 min read
Vue.js logo over a dark, textured purple background. The article discusses using defineExpose and in Vue 3 to enhance component interaction and enable dynamic theming.

defineExpose and <style vars> in Vue 3 for component interaction and theming

Simplify component interaction and dynamic theming in Vue 3 with defineExpose and for better control and flexibility.

Clara Ekekenta
Nov 7, 2024 ⋅ 8 min read
View all posts

2 Replies to "Using RxJS Observables to transform data in TypeScript"

  1. Svelte is a much better system for Observables. It requires setting up its dev tools. As it compiles observable code according to how it is being used.

    With rxjs, never ever use subscribe or unsubscribe yourself. Leave it to a framework such as Angular. Don’t put yourself in a place that a memory leak could happen. Even if it never does. Knockout.js deprecation is a good example why.

  2. Yes, this is something I agree with.
    Managing subscriptions ourselves can be risky because we might forget to unsubscribe from the Observable, resulting in a memory leak.

    Svelte manages our subscriptions on our behalf. This, in my opinion, makes it one of the most reactive frameworks.

    Considering Node.js where there are no native Observables, we are left to manage subscriptions ourselves.

Leave a Reply