Proposal for signal-based API standard
Proposal for signal-based API standard
github.com
GitHub - proposal-signals/proposal-signals: A proposal to add signals to JavaScript.
12 comments
12 comments
Proposal for signal-based API standard
GitHub - proposal-signals/proposal-signals: A proposal to add signals to JavaScript.
Basically reactifying JS? I've found it very hard to read react code and find out where an event / signal comes from. Somewhere, something changes and at some other place it has an effect. Probably because I abandoned JS a long time ago, I'm not up to date on the advantages of react, but JS nowadays has never been harder to read.
CC BY-NC-SA 4.0
JS just feels like anarchy to me with how certain events/methods work.
whispers because it is
No, not reactifying JS. That's not the intent of this as I interpret it. Take a moment to read through the whole thing and I'm sure any fears you have about this should go away. This is mainly for framework authors, rather than application developers. A standardized and optimized way to code reactivity, reducing framework bundle size, reducing bugs, among other things, no need for weird hooks or Proxy objects and things like that. Good stuff.
Maybe even one day React will have property support.