Re:A proposal to add signals to JavaScript
by throwitaway1123 on Sunday March 31, 2024 @03:11PM
(#39887118)
I think the comment you're replying to is referring to the pub/sub sections of the proposal. They don't explicitly mention events, but events are a subset of the publish/subscribe pattern.
[ Parent
| on HN ]
Re:A proposal to add signals to JavaScript
by explaininjs on Sunday March 31, 2024 @03:14PM
(#39887138)
But then so are signals.
The only "benefit" signals as proposed here give you is less control over the exact dispatch pattern of the graph, for instance things like debouncing, throttling, batching, etc etc etc. Aka all the things you absolutely must have control over if you want to make something resembling a high performance application.
Re:A proposal to add signals to JavaScript
by naasking on Sunday March 31, 2024 @03:25PM
(#39887250)
Signals are not a subset of events. Signals combine event subscription with value construction, which promotes a remote declarative model for updates.
> The only "benefit" signals as proposed here give you is less control over the exact dispatch pattern of the graph, for instance things like debouncing, throttling, batching,
Events don't give you any more control over those properties than signals, they just require more boilerplate.