Netflix JavaScript Talks - Async JavaScript with Reactive Extensions

Channel:Matt Marenghi · Length:28:38 · Published:2014-03-22 · Views:69506

Watch on YouTube

Summary

A Netflix JavaScript talk on using Reactive Extensions (Rx) for asynchronous UI code. It covers Observables, composing events such as drag and drop, and sequencing Ajax requests.

Why HN recommends it

Recommended as a clear, mind-changing introduction to observables and async programming from engineers using Rx in production.

have a look at this presentation about Observables at Netflix as it's quite mind changing — HN, 2016

Functional programming · Web development

Subtitles (excerpt)

so I'm going to talk to you today about our experiences with async JavaScript at Netflix now uh all of us JavaScript programmers have experience with async programming um so first a little bit about me uh I'm the cross team technical lead for Netflix so I work across all the various Netflix uis um the V majority of which as Matt mentioned are written in JavaScript I got about 13 years in the industry formerly worked at GE and Microsoft and I've got about six years under my belt uh doing functional reactive programming uh Building Systems that is so this is really the story of how Netflix solved big async Problems by thinking differently about events and so our app and in fact most JavaScript apps are very asynchronous right we have all these modules with app startup where we're coordinating waiting for platform components to come up and we're waiting for things to come back from the web we have the player in which you can play and then cancel we have data access going on at all times we've got animations to coordinate we've got our view to buy to a model all these things are asynchronous processes and they can really if you don't get them under control they can really cause you app complexity to just

On Hacker News

I don't really like await . It seems to be a syntactical fix which acts in a quite magical way. Not sure if introducing magic to a language syntax is what we want. Rather, we should think about data flow of our async apps differently. I believe Observables are the future of async code. Once you grasp the concept that everything in your app can be transformed into streams of events, and you work w… — sktrdie, 2016-06
The conf talk on youtube by Matt Marenghi [linked in the post] is really awesome. Provides great examples and resources. Really worth 28-min. Direct Link: [VIDEO] — film42, 2014-05
Yes I meant what "Reactive Extensions" does. Should've been clearer that it was a reference to "functional reactive programming" and not a specific library. edit: "Async Javascript at Netflix" is a great talk on this - [VIDEO] — sriku, 2014-07
i thought it was a good presentation, however, I recently watched a Netflix one, published by Matt Marenghi, which to me was infinitely better. I think the description of events as just another collection, albeit a time based collection flow was nicer ( Observable === Collection + Time ), and also that this collection must have the ability to tell you that it has terminated. [VIDEO] — shaydoc, 2014-06
It's not a fad at all, with Netflix and other companies using Rx in all flavors on their platforms. See this video from Jafar Husain, a tech lead at Netflix, talk about how they use RxJS at Netflix: [VIDEO] — mattpodwysocki, 2014-06

Related videos