The effect of React on web standards
summary
Claims that React’s ideas push concrete ECMAScript features into the language, with actual proposals and polyfills shipping — examples include JSX inspiring template-less patterns, rest/spread and class fields moving into spec, and optional chaining under consideration — and tools that reuse JS as an intermediary format so libraries interoperate. The component model and unidirectional data flow become low-level proposals; integration experiments use shadow DOM and custom elements as leaf components, with some specs adopted and others stalled.
AI-written summary · about
chapters (24)
- 0:00Start
- 9:33The web standards process is fundamentally different than library API development with a single owner and monoculture
- 10:22Discontent & New Approaches
- 13:11New Approaches Prototype, jQuery, Dojo, MooTools (2005-6)
- 16:26React (2013) New and Improved Paradigms
- 16:53React: Paradigms Data binding Forget about the implementation details of data binding
- 17:55React: Paradigms Virtual DOM Re-render everything without the performance hit
- 19:52roots in functional programming pragmatic functional approach
- 20:32While it is influenced by ... functional programming, staying accessible to ... developers with different skills and experience levels is an explicit goal of the project. -React Docs
- 20:51React: Paradigms Immutability, Unidirectional Data Flow Less power over data interactions is easier to reason about
- 22:41React Embracing Web Standards
- 24:07React Curating Web Standards
- 24:55React Discontent with Standards
- 26:39custom elements templates • shadow DOM • HTML Imports
- 28:02shadow DOM encapsulation could become interoperable standard
- 29:08most web components assume imperative API • no focus on composability
- 29:50Web Standards Proposals
- 31:28Stage 3 (candidate): signed-off spec text, needs implementations and user feedback
- 44:43Expose more APIs [that browsers already implement]. That's what the extensible web manifesto is all about. And that's really good.
- 46:44React is awesome and drives a ton of discussion among folks who work on Web Components. -Rob Dodson, Regarding the broken promise of Web Components
- 47:01Future Integration efforts
- 48:15Future Alternative Specifications
- 48:56Future Alternatives to the DOM
- 50:17Future New languages
