5 ms·

> There's always a multitude of ways to get something done, and it's up to you to decide what tool will do it best Well said. By the way, what is Netflix's ta

> There's always a multitude of ways to get something done, and it's up to you to decide what tool will do it best Well said. By the way, what is Netflix's take on Promises vs RxJS?

ZoeZoeBee 10y ago
I'm pretty sure Netflix is in the Observables camp, as Ben Lesh over at Netflix is RxJs
- Akkuma 10y ago
  I watched one of the recent Netflix engineering videos where they moved to a customized version of React and I could have sworn in that talk they actually moved away from Observables[1]. What was confusing is that the other talked released at the same time they talk about enhancing RxJS. [1]: https://youtu.be/5sETJs2_jwo?t=5m32s https://youtu.be/5sETJs2_jwo?t=5m32s
  - mikeryan 10y ago
    A friend of mine runs some UI engineering at Netflix from talking to him reactive JavaScript is still heavily used.
    - Akkuma 10y ago
      I'm sure it is still heavily used, but it looks like there are two very opposing views with one going so far as completely removing it.
tylerlh 10y ago
One of the core tenets of the Netflix culture is "Freedom & Responsibility". In this context it means that each team is free to make calls like that as they see fit. Promises, Observables, Generators, Callbacks -- it's up to your team to determine what makes the most sense. That said, we do make heavy use of Rx on the API layer (RxJava/RxGroovy). My team isn't currently using RxJs, but I expect that to change in the future. There are a lot of Observable fans here :)
zamalek 10y ago
> By the way, what is Netflix's take on Promises vs RxJS? We've been doing tons of research into the Netflix methodology and teams are highly compartmentalized (albeit communicate richly). This means that when you ask "What do you do at Netflix?" you should really be asking "What does team X do at Netflix?" or "Does any team at Netflix do X?" For instance, unless things have changed or I have the story wrong, JVM is used for the streaming because that's the tool which that team chose. The other teams merely communicate with it over an API (regardless of client language).

> There's always a multitude of ways to get something done, and it's up to you to decide what tool will do it best Well said. By the way, what is Netflix's take on Promises vs RxJS?

ZoeZoeBee 10y ago

I'm pretty sure Netflix is in the Observables camp, as Ben Lesh over at Netflix is RxJs

Akkuma 10y ago
I watched one of the recent Netflix engineering videos where they moved to a customized version of React and I could have sworn in that talk they actually moved away from Observables[1]. What was confusing is that the other talked released at the same time they talk about enhancing RxJS. [1]: https://youtu.be/5sETJs2_jwo?t=5m32s https://youtu.be/5sETJs2_jwo?t=5m32s
- mikeryan 10y ago
  A friend of mine runs some UI engineering at Netflix from talking to him reactive JavaScript is still heavily used.
  - Akkuma 10y ago
    I'm sure it is still heavily used, but it looks like there are two very opposing views with one going so far as completely removing it.

tylerlh 10y ago

One of the core tenets of the Netflix culture is "Freedom & Responsibility". In this context it means that each team is free to make calls like that as they see fit. Promises, Observables, Generators, Callbacks -- it's up to your team to determine what makes the most sense. That said, we do make heavy use of Rx on the API layer (RxJava/RxGroovy). My team isn't currently using RxJs, but I expect that to change in the future. There are a lot of Observable fans here :)

zamalek 10y ago

> By the way, what is Netflix's take on Promises vs RxJS? We've been doing tons of research into the Netflix methodology and teams are highly compartmentalized (albeit communicate richly). This means that when you ask "What do you do at Netflix?" you should really be asking "What does team X do at Netflix?" or "Does any team at Netflix do X?" For instance, unless things have changed or I have the story wrong, JVM is used for the streaming because that's the tool which that team chose. The other teams merely communicate with it over an API (regardless of client language).