Am I only streaming? Thinking reactive

on YouTube ↗03m

" summary

Claims that reactive is a practical evolution of 1978 CSP and 1973 actor ideas, reframing systems as data flows and transformations and showing reactive architectures are fractal across layers. Demonstrates patterns and tools like Erlang and Akka, cites real failure modes (left-pad on NPM, hidden Maven/shared-assembly dependencies) to justify duplicate over wrong abstraction as a pragmatic choice, and argues abstractions live on a continuum rather than being simply right or wrong.

AI-written summary · about

" related talks

• 42mReacting to the Future of Application ArchitectureGrace Jansen · W-JAX 2019
• 48mReactive for the ImpatientMary Grygleski · Windcity DevFest 2019
• 01h 04mFrom Functional to Reactive ProgrammingVenkat Subramaniam · Riga Dev Days 2019
• 01h 42mWhat is a Reactive Application?Viktor Klang, Martin Thompson, Kresten Krab Thorup, Todd Montgomery · GOTO Copenhagen 2014
• 50mThe reactive landscapeClement Escoffier · Jfokus 2018
• 41mThe definite guide to reactive programming in JavaErwin de Gier · Codemotion Rome 2018
• 01h 11mReactive Architecture Patterns DebateJakub Marchwicki · Global Software Architecture Summit 2019
• 45mReactive for the Impatient - A Gentle Intro to Reactive Programming and SystemsMary Grygleski · Greach 2019