3 ms·
No, they don't. In fact, if you search "event" in the proposal you get exactly one result, the prefix of "eventually". This is a serious shortcoming of the prop
by explaininjs 3y ago
No, they don't. In fact, if you search "event" in the proposal you get exactly one result, the prefix of "eventually". This is a serious shortcoming of the proposal that should be addressed.
- throwitaway1123 3y agoI 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.
- explaininjs 3y agoBut 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.
- naasking 3y agoSignals 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.
- ivan_gammel 3y agoOh, come on. They do have an example of architecture, not literal example of events. It doesn’t matter what trivial implementation of Observer pattern you choose.
- explaininjs 3y agoExcept one is already built into the language? And it provides all the upsides of signals with none of the downsides? (Modulo proper use of `using` directives)
- deleted 3y ago[deleted]
- deleted 3y ago[deleted]