React.js Conf 2015 - The complementarity of React and Web Components
Meta Developers1 HN recommender · recommended in 1 month, 2015–2015
talk · intermediate · 2015–2015 on HN
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.
Cited in React versus Web Components threads as a clear picture of how the two interoperate and their challenges.
Up next
14 mo on HNWhat the heck is the event loop anyway? | Philip Roberts | JSConf EU
JSConf
16 HN recommender · 2015–2025
13 mo on HNRich Harris - Rethinking reactivity
You Gotta Love Frontend
15 HN recommender · 2019–2026
10 mo on HNCrockford on JavaScript - Volume 1: The Early Years
YUI Library
10 HN recommender · 2013–2022
10 mo on HNRailsConf 2016 - Turbolinks 5: I Can’t Believe It’s Not Native! by Sam Stephenson
Confreaks
6 HN recommender · 2017–2020
10 mo on HNJavaScript: The Good Parts
Google TechTalks
11 HN recommender · 2009–2020
9 mo on HNPete Hunt: React: Rethinking best practices -- JSConf EU
JSConf
9 HN recommender · 2014–2025
8 mo on HNDan Abramov - Live React: Hot Reloading with Time Travel at react-europe 2015
ReactEurope
12 HN recommender · 2015–2022
7 mo on HNHey Underscore, You're Doing It Wrong!
InfoQ
9 HN recommender · 2014–2022
6 mo on HNChris McCord - Keynote: Phoenix LiveView - Interactive Apps without Javascript - ElixirConf EU 2019
Code Sync
4 HN recommender · 2019–2024
6 mo on HNOAuth 2.0 and OpenID Connect (in plain English)
OktaDev
7 HN recommender · 2019–2026
6 mo on HNJake Archibald on the web browser event loop, setTimeout, micro tasks, requestAnimationFrame, ...
JSConf
7 HN recommender · 2018–2023
6 mo on HNRiftSketch: Live coding in VR with the Oculus Rift, Firefox WebVR, JavaScript and Three.js
Brian Peiris
5 HN recommender · 2014–2020
3 comments from Hacker News
Exactly which part of that thread leads you to believe that "React plays just fine with Web Components". I suggest you watch ▶ this 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
You could just use Web Components within your React views; 'React.js Conf 2015 - The complementarity of React and Web Components' - ▶ this video
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 ( ▶ this 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?