))
TC39: How signals work, adding signals to the JavaScript programming language
Manage episode 493171472 series 3676184
Content provided by Tejas Kumar. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Tejas Kumar or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.
Links
- Codecrafters (sponsor): https://tej.as/codecrafters
- TC39 Signals Proposal: https://github.com/tc39/proposal-signals
Summary
In this conversation, Kristen Maevyn, and Daniel Ehrenberg discuss reactivity and its importance in JavaScript. They explore the concept of reactivity, its role in keeping applications deterministic, and the challenges of achieving consistency in modern rendering frameworks. They also compare signals to observables and explain why signals are being considered as a language-level feature.
The conversation touches on the API for signals, the use of classes in JavaScript, and the benefits of functional programming. Signals are an evolution of the long-standing problem of managing state in JavaScript applications. They provide a solution to the issues with classes and functions by combining the benefits of both. Signals allow for encapsulation, testing in isolation, and pure functions while still being able to handle state.
Chapters
00:00:00 Intro
00:09:57 What are signals?
00:26:37 Classes and the `new` keyword
00:41:31 State Management and Signals
00:49:25 Push-based vs. Pull-based Reactivity
01:04:43 Language-level vs. Framework-level Signals
01:14:27 Server-side Signals
01:25:06 Self-referencing Signals
01:36:29 Audience Q&A
01:47:07 Conclusion
Hosted on Acast. See acast.com/privacy for more information.
88 episodes
Share
