Member-only story
JS New Proposal “Signals” Future Plan for 2015
This document describes the early general direction of Signal in JavaScript, similar to the Promises/A + work before the TC39 standardized Promise in ES2015. Try it yourself and use polyfill.
Similar to Promises/A +, the focus of this work is to adjust the JavaScript ecosystem. If this adjustment is successful, a standard may emerge based on this experience. Several framework authors are collaborating to develop a universal model that can support their reactive core. The current draft is based on the design input of authors/maintainers such as Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, etc.
Unlike Promises/A +, we are not asking to solve a general developer-oriented surface API, but to solve the precise core semantics of the underlying Signal graph. This proposal does include a completely specific API, but it is not aimed at most application developers. Instead, the Signal API here is more suitable for building frameworks that provide interoperability through a general Signal graph and automatic tracking mechanism.
The plan for this proposal is to conduct important early prototyping before entering Phase 1, including integration into multiple frameworks. We are only interested in standardizing Signal when it is suitable for practical use in multiple frameworks and provides real benefits over Signal provided by the framework. We hope that important early prototyping can provide us with this information. For more information, please…