Signals have moved beyond the "hot new thing" to become "just how every framework except React works". What's next? One option is to stabilize the ecosystem, increase performance and interoperability by making Signals built-in to JavaScript, like Promises. But... it'd be good to avoid some of the pitfalls of Promises, such as their always-on scheduler. This talk gives a brief introduction to TC39, the JavaScript standards committee, and spends most of its time showing off the early proposed Signal API, describing how it has been developed so far and how you can get involved and help.
Your name (and pronouns)
Kristen Maevyn (she/her) and Shay Lewis (they/them)
Location
NYC
Contact Details
Get in touch via Daniel Ehrenberg @ littledan1337 on Discord, or dehrenberg@bloomberg.net
Talk title
Standard Signals in JavaScript?
Abstract
Signals have moved beyond the "hot new thing" to become "just how every framework except React works". What's next? One option is to stabilize the ecosystem, increase performance and interoperability by making Signals built-in to JavaScript, like Promises. But... it'd be good to avoid some of the pitfalls of Promises, such as their always-on scheduler. This talk gives a brief introduction to TC39, the JavaScript standards committee, and spends most of its time showing off the early proposed Signal API, describing how it has been developed so far and how you can get involved and help.
Your name (and pronouns)
Kristen Maevyn (she/her) and Shay Lewis (they/them)
Location
NYC
Contact Details
Get in touch via Daniel Ehrenberg @ littledan1337 on Discord, or dehrenberg@bloomberg.net
Code of Conduct