HackerTube.dev

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

Meta Developers · 26.2K views · 2015-02-04 · 25:55

Open on YouTube ↗

If playback is restricted in your region, try opening the original video. Use Mark watched to add it to your marked videos.

Overview

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.

On Hacker News

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

Recommended by 2 HN people across 2 months · HN mentions 2015–2017

Topics

Search by tags

What people said

mikeryan · 2015-06 · Recommendation

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]

Read the original HN comment ↗
peterhunt · 2015-02 · Recommendation

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 :) [LINK]

Read the original HN comment ↗
sscotth · 2017-03 · Reference

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 environments with React Native, NativeScript, Titanium... Here are several examples where JSX is used that is not a browser: - Native desktop apps for Linux, Mac, and Windows (Not including Electron/NW.js)[1][2][3][4] - TVs with AppleTV apps or Netflix's Gibbon[5][6] - Command line apps as stdin/stdout with react-blessed[7]/mylittledom[8] - Direct to Canvas[9]/pixi.js[10] - Latex documents[11] - Web Audio[12] - Conole.logs[13] - Truly custom direct to hardware[14] as some C code like: `digitalWrite(led, HIGH)` I definitely believe JSX could use standardization separate from any implementation, JavaScript or otherwise. [0]: [LINK] [1]: [LINK] [2]: [LINK] [3]: [LINK] [4]: [LINK] [5]: [LINK] [6]: [VIDEO] [7]: [LINK] [8]: [LINK] [9]: [LINK] [10]: [LINK] [11]: [LINK] [12]: [LINK] [13]: [LINK] [14]: [LINK]

Read the original HN comment ↗

Sources

Video by Meta Developers, played through YouTube.

Data and selection notes

HN summaries and labels may contain AI errors. HN dates refer to discussions, not video publication.

HN Library: HackerTube export (2026-10-31) and open-index/hacker-news. Upstream summaries and classifications may contain AI errors.

Views, duration and playback status refresh separately from the published catalog. When an update fails, existing data remains visible.

Selection checks
  • SaaS & AI candidates: Topic keywords do not match
  • Editor-approved picks: Editorial review is required

Rule matches identify candidates. They do not guarantee video quality or financial results.

About the library and its sources