react native

Fernando Rojo explains how BeatGig reached $10M in sales with one frontend engineer by sharing code between React Native and Next.js, covering navigation, animation, theming and performance.

Microsoft engineers Chiara Mooney and Shiven Mian describe the journey and challenges of building and consuming React Native for Windows inside Microsoft. It was given at Chain React 2023.

Ben Alpert of the React team talks at React.js Conf 2016 about where React is heading. He covers performance and stability work, challenges at Facebook, and opportunities such as bringing React Native ideas to the web.

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.

Dan Abramov live-codes hot reloading with time-travel debugging at React Europe 2015, debuting Redux and its devtools. The slides themselves are driven by application state.

Pete Hunt of Facebook and Instagram introduces React at JSConf EU 2013 and explains its design principles. He argues that separating templates from logic only separates technologies, not concerns, and makes the case for components.

Pete Hunt of Facebook and Instagram presents React at JSConf.Asia 2013, explaining its design principles and why they seemed shocking at first. He argues that React separates concerns rather than technologies, and the talk also announces the React Chrome developer tools.

Lee Byron of Facebook explains how persistent immutable data structures work and how to use them in React apps with Immutable.js. He covers memoization benefits and avoiding coupling through shared mutable state.

Jordan Walke, creator of React, talks at ReasonConf 2019 about the ideas behind ReasonML and how it extends React's programming model with OCaml. He also discusses why familiar syntax matters.

David Guillot describes how his team replaced a two-year-old React UI of their SaaS product with Django templates and htmx in a couple of months. The talk gives concrete indicators on code size, performance and team impact.

Lin Clark gives an illustrated, cartoon-style walkthrough of React Fiber, the rewrite of React's reconciler, explaining its incremental rendering and scheduling at React Conf 2017.

Professor Ruzic explains modular micro-reactors: self-contained nuclear units with passive safety whose fuel lasts about 20 years. He covers their use for process and district heat and where they can compete with diesel generation.

Pete Hunt explains why React's virtual DOM was built, how it compares with databinding-style systems, and what it means for future browser technology. Recorded at FutureJS 2014 in Barcelona.

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.

A 2008 Google Tech Talk making the case for the liquid fluoride thorium reactor as an abundant, safe source of electrical power. It covers the technical motivations and design of thorium molten-salt reactors.

Ryan Florence's React.js Conf 2015 talk pushes React into unusual use cases, including a demo comparing rendering in React, Ember and Angular.

Svelte creator Rich Harris explains moving reactivity into the compiler and language rather than tracking state at runtime, with a history of spreadsheets as reactive systems and comparisons to React.

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.

Dan Abramov's JSConf Iceland talk on what came after React 16, with live-coded prototypes of async rendering and time slicing. It previews the ideas that became concurrent mode and suspense.

David Nolen explains how ClojureScript is used at Vouch.io to build mobile and web software with a single language and REPL-driven workflow. The talk includes a live coding demo of React Native development.

Cheng Lou's react-europe 2016 talk lays out a mental framework for thinking about abstraction levels in JavaScript tooling, from Angular and Grunt to Webpack and React. It uses that framework to reason about the cost of abstractions and how to choose between competing solutions.

Kirk Sorensen's Google Tech Talk on thorium molten-salt reactors (LFTR). He covers why the technology was shelved after early development and argues that now is the right time to revisit it.

Jafar Husain's ACM keynote presents Netflix's JSON Graph and Falcor, which let web developers treat all cloud data as one virtual JSON model. It combines reactive programming with REST principles.

Sam Stephenson's RailsConf 2016 talk on Turbolinks 5, showing how small teams can ship fast Rails apps in the browser and hybrid iOS and Android apps sharing one set of web views.

Fons van der Plas introduces Pluto.jl, a reactive notebook for Julia that tracks references between cells and re-runs affected cells when code changes. The talk was given at JuliaCon 2020.

Facebook engineers explain why they abandoned the traditional MVC paradigm for a more functional architecture, introducing Flux and React. They use the unread-message-count bug as a case study of the problems of bidirectional data flow at scale.

Sebastian Markbage explains how React is moving toward a minimal API surface by leaning on language features and patterns instead of dedicated framework APIs. He also touches on JSX and syntax proposals for future JavaScript.

Tom Caputi presents the design of native encryption for ZFS at the OpenZFS Developer Summit, including design decisions and how authentication uses checksum fields.

Evan Czaplicki's Strange Loop 2014 talk surveys the many formulations of functional reactive programming and how they relate historically and theoretically. It then shows how Elm's variant enables hot-swapping and its time-traveling debugger.

Tom Dale explains the internals of the Glimmer VM, Ember's rendering engine, which compiles templates to opcodes. The talk includes a performance benchmark demo.

Corridor Crew VFX artists react to the visual effects of the 2021 Dune and compare them with David Lynch's 1984 version. They discuss which effects were practical and which were CGI.

A BBC Four documentary following Alan Bond and Reaction Engines as they pursue the Skylon spaceplane and its SABRE engine. It covers the history from HOTOL and the heat-exchanger breakthrough.

Erik Meijer gives a provocative talk presenting what he calls a rational alternative to Agile, arguing against Scrum-style practice. He also touches on the tenth-man concept.

A professor from Illinois compares the cost of building, fueling and operating a nuclear plant against a natural gas plant, using visual charts. It shows how construction time and interest rates dominate, when the investment pays off and when costs cross over.

Real Engineering's Brian McManus explains Helion's approach to nuclear fusion: colliding two plasma rings, compressing them magnetically, and capturing energy directly from the changing magnetic flux rather than boiling water. It covers why this pulsed design sidesteps problems of tokamaks and laser fusion.

Yaron Minsky of Jane Street shows how the OCaml Incremental library lets trading UIs express data transformations that are easy to read and efficient on streaming data. It includes a live table demo.

A Ukrainian documentary about the liquidators who cleaned radioactive debris off the Chernobyl reactor roof in two-minute shifts. It presents their firsthand accounts and footage of the work.

Kirsten Dirksen tours new Earthships, homes built from tires, bottles and cans that generate their own energy, collect water and grow food. The video covers the newer, cheaper Encounter model and its passive systems.

Matthew Griffith, creator of elm-ui, presents a toolkit for designing layouts in Elm as an alternative to CSS. He explains the opinionated approach to layout and styling.

MIT 22.01 lecture by Michael Short explaining the Chernobyl accident technically, including RBMK reactor positive feedback, xenon poisoning and the cascade of human errors during the test.