React.js Conf 2015 - Beyond the DOM: How Netflix plans to enhance your television experience

Channel:Meta Developers · Length:25:54 · Published:2015-02-04 · Views:26241

Watch on YouTube

Summary

Jafar Husain of Netflix explains at React.js Conf 2015 how Netflix runs React-style rendering without the DOM on smart TVs and game consoles. It uses a canvas-like API for performance.

Why HN recommends it

Cited as the primary source on React with a custom rendering backend and on Netflix's Gibbon engine.

There's an interesting video by Netflix where they discuss using React in their stack. — HN, 2015

Web development · Software performance & optimization

Subtitles (excerpt)

hey everybody yes so I was going to come in and totally blow your mind and uh mention that react can Target things other than the Dom and uh yeah thanks Christopher that's great um well today I'm going to talk to you about react beyond the dawn but we're actually going to go in a little more technical detail than Christopher did we're actually going to take a look at some of react's extensibility points um so first of all a little bit about me I'm the cross team Tech lead for the Netflix U um I'm the architect of Netflix's UI data platform and uh I'm member of the tc39 so for those you don't know it's the JavaScript standards committee and so you know we're helping shepher some of the cool es6 features that you guys saw today um yeah so this is the story of how Netflix pushed react into places where the Dom could not go and specifically I'm talking about things like embedded devices so before we start though three things you guys may not know about Netflix first we love JavaScript we use JavaScript everywhere and there's a lot of reasons for that the first is that Netflix runs on thousands of devices we want to be wherever you are and whatever device you're using whether it's in your pocket in your hand or a hologram or you

On Hacker News

There's an interesting video by Netflix where they discuss using React in their stack. To increase performance on many of Netflix's TV or Console based UI's they have their own rendering engine they're using instead of the manufacturer's browser engine. This means any of React's "speed" improvements are a moot point so instead they use it because of its simplicity for UI layouts. [VIDEO] — mikeryan, 2015-06
If you're interested in doing it with React, here's a video explaining how to do a custom backend: [VIDEO] You basically need to change BackendIDOperations and ReactEventListener to send/receive messages vs talking to the real APIs. It's already set up in the codebase to do this (because it actually worked at one time). Webpack, per usual, already thought of this and has an answer for you :) [LIN… — peterhunt, 2015-02
Its also important to consider the environment as well since JSX is potentially much bigger than the web. JSX is much like other generic user interface markup languages[0] and like many other is simply a dialect of XML. Any interface that can be represented with XML/HTML or any other markup language can use JSX and optionally react. We are already seeing this boom with in native mobile environmen… — sscotth, 2017-03
Sorry. I was under the impression after watching this video Netflix was using React across all devices. [0] [0] [VIDEO] — zappo2938, 2017-01
Picking a nit, they don't use React in the browser across all devices. They actually use an internal rendering engine called Gibbon on some devices with client code written JavaScript with React but not rendering to HTML or a browser instead using their internal engine. Interestingly this has become easier with React breaking out React and ReactDOM. Interesting to note that Netflix must see Gibbo… — mikeryan, 2015-11

Related videos