HackerTube.dev

React.js Conf 2015 - The complementarity of React and Web Components

Meta Developers · 21.6K views · 2015-02-03 · 25:47

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

Andrew Rota of Wayfair argues at React.js Conf 2015 that React and native Web Components complement each other. He shows how they can be combined for complex web applications.

On Hacker News

Cited in React versus Web Components threads as a clear picture of how the two interoperate and their challenges.

Recommended by 1 HN people across 1 months · HN mentions 2015–2015

Topics

Web development
Search by tags
reactweb componentsinteroperabilityfrontendreactjsconf

What people said

marknutter · 2015-02 · Recommendation

Exactly which part of that thread leads you to believe that "React plays just fine with Web Components". I suggest you watch [VIDEO] which gives a very clear picture of the current state of React/Web Component interaction, including the challenges associated with it. edit: another good read if you're interested: [LINK]

Read the original HN comment ↗
jimmcslim · 2015-07 · Reference

You could just use Web Components within your React views; 'React.js Conf 2015 - The complementarity of React and Web Components' - [VIDEO]

Read the original HN comment ↗
nutate · 2015-03 · Reference

Good clickbait, but almost nonsensical article. The idea of supporting web components is great, but it's also a standards process in committee. React and Web Components can play together ( [VIDEO] ), so why draw some sort of false dichotomy between the technologies. The thought that went into the virtual dom diffing strategy is an algorithmic nicety that software in general can and has already benefitted from. React itself is an implementation of that which provides real workflow improvements for web and now native platforms. That's pretty awesome and usable right now. I don't see this as a zero sum game, or as an all in investment strategy unless you are going into some arcane questions of licensing, the code and the ideas are out in the open. Ember, mythril, Om have all taken the ideas into new regions. Even look at the atom editor, they switched to react for their editor component, then realized the general purpose dom diffing strategy which is very fast could still be optimized for their edit window. That's awesome. That idea is decoupled from react. Learning to read react code takes about 1 day to 1 week. It's pretty awesome. Also, the canard about reactive programming... uhh... I just don't get what you're advertising here? That you're willing to use products like docker and node.js as advertised on your front page, but not react.js because... it's "bad"? Why so inflexible, why not try all the things and use what works as time permits?

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