async javascript

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.

Steve Klabnik walks through the history of Rust and how its design evolved toward async/await, including the alternatives tried and dropped. He also discusses the difficulty of adding a major feature to a language.

Without Boats, a Rust language team member, explains the design of Rust's async/await at RustLatam 2019. He covers the history and constraints behind zero-cost, allocation-free async state machines.

James Mickens delivers his comedic rant about JavaScript and web programming, in his usual dry, hyperbolic style. It includes his account of learning the language from the O'Reilly Definitive Guide.

David Beazley's workshop screencast builds asynchronous programming in Python from scratch, starting from callbacks and continuations and replacing threads to show how concurrency works underneath.

Zig creator Andrew Kelley's RedisConf 2020 talk on modeling data flow with asynchronous I/O in Zig. It explains how Zig's async/await avoids function coloring, and Loris Cro demonstrates OkRedis, a zero-allocation Redis client.

Nathaniel J. Smith's PyCon 2018 talk introducing Trio, a Python concurrency library designed around usability and structured concurrency. He live-codes a problem and analyzes pitfalls in other async libraries.

Ryan Dahl's JSConf EU talk introducing Node.js to the world. He explains the motivation for event-driven, non-blocking I/O, with JavaScript chosen mainly for its asynchronous nature.

Nicholas Zakas of Yahoo discusses architecture for large, modular JavaScript web applications. He lays out the theory behind building front ends that scale in complexity.

A Channel 9 conversation recorded at GOTO 2012 between Anders Hejlsberg (TypeScript) and Lars Bak (Dart). They discuss the two languages and different approaches to making JavaScript development safer, including runtime type checking.

A short screencast tour of JSPM, SystemJS and ES6 features, building a small app with the then-new JavaScript module and package tooling. It shows how JSPM works as a package manager, bundler and loader.

Douglas Crockford's Nordic.js 2014 talk on 'the better parts' of JavaScript and programming in general. He argues against `this`, `new` and ES6 classes, and for classless, composition-based object patterns, with some broader remarks on building better structures for the future.

Jonathan Worthington's YAPC Asia 2015 talk on parallelism, concurrency and asynchrony in Perl 6. It covers the language's concurrency features.

Andreas Kling live-codes a prototype JavaScript JIT compiler for the LibJS engine used in SerenityOS and Ladybird. He builds a standalone bytecode VM, a simple interpreter, and then a simple JIT in about 80 minutes.

Paul Irish explains how pointerpointer.com works. It uses a hidden canvas of colored Voronoi regions to look up which photo matches the cursor position.

The original 2012 screencast introducing Meteor, a JavaScript framework for building web apps quickly. It demonstrates realtime updates, latency compensation and low boilerplate.

Omar Rizwan's short !!Con talk about writing a Breakout game in JavaScript that runs inside a PDF. It explores the surprisingly large PDF specification, including its scripting support.

Chris McCord's ElixirConf EU 2019 keynote introducing Phoenix LiveView, which builds interactive server-rendered apps without writing JavaScript. It explains how only changed dynamic parts are sent over a websocket.

Jon Gjengset's long live-coding stream explains Rust's Pin and Unpin types: why they exist, how they work, and how they connect to futures and async/await. It also covers moving from pre-pinning code to the new model.

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.

Andrew Kelley's 2024 Zig roadmap talk, followed by a Q&A, covers the language's priorities and the state of the project. Topics include compilation speed, moving off LLVM toward a self-hosted toolchain, async, and the path to 1.0.

Rafal Dittwald's Clojure/north talk shows how to move from writing Java-style code in Clojure to thinking in data-driven, functional terms. He walks through a JavaScript example, refactoring imperative code step by step into a functional core.

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.

Ron Pressler's Curry On 2015 talk arguing that imperative languages should not be polluted with pure functional concepts like monads. He favors simple blocking code over non-blocking styles.

A JSConf 2014 talk visually breaking down algorithms behind everyday UI patterns, such as dropdown menus that vanish when the mouse drifts and picking the nearest target to the cursor. It shows how these are implemented in JavaScript.

Derek Slager's Clojure/conj talk argues that ClojureScript is a pragmatic choice for web development. He addresses common objections, recent improvements, tooling and use cases where it shines.

Photopea founder Ivan Kutskir talks about developing a free browser-based photo editor, one of the most complex JavaScript programs ever written, and the web technologies behind it.

C J Silverio, former npm CTO, explains how the JavaScript package commons ended up in the hands of a for-profit company with no accountability. She discusses the cost of running a registry and what the community should do next.

Douglas Crockford's YUIConf 2012 evening keynote tries to explain monads in a way programmers can actually understand, in the context of JavaScript. He aims to break the 'monad tutorial curse'.

A Rubber Duck Engineering episode on the years before Flutter, covering web projects and three JavaScript frameworks that influenced it, and the early DOM-based, network-loaded Flutter.

Steve Yegge is interviewed at Google's Kirkland office about the birth, growth and future of his Rhino on Rails project, a Rails clone on the Rhino JavaScript engine, and other web development topics.

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.

Dylan Beattie's entertaining NDC talk imagines an alternate history of the web, asking what if different decisions had been made on operating systems, browsers and standards. It blends real history with humor.

Alex Russell's Chrome Dev Summit 2016 talk on building web experiences that work on slow, flaky networks and low-power devices. It argues developers should focus on the performance of real-world mobile hardware rather than desktop machines.

James Long's dotJS 2019 talk on how CRDTs enable local-first apps and how simple they can be to implement. He shows how to use them to build robust offline-capable frontends.

Ryan Dahl tells the history of Node.js and why he created it at a Phoenix meetup. He explains the push for non-blocking IO on a clean slate rather than extending an existing ecosystem.

Douglas Crockford tells how JSON was discovered rather than invented, and how its simplicity made it a dominant data interchange format. He also covers surrounding history such as earlier Netscape usage and the 'Good, not Evil' license story.

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.

A five-minute video showing how to build a counter in the Imba web programming language in under a minute, then style it.

A dotJS 2012 conference talk by Fat (of Twitter Bootstrap fame) on what open source really means and why maintainers feel guilty about it. It covers the obligations, expectations and burnout that come with releasing popular open source software, delivered with humor.