Simplify code in examples. Replace code like const isEven = () => (counter & 1) == 0; to something like const isEven = () => (counter % 2) == 0;
When i read this example, i feel straightforward overengineering and even don't want to read description.
Proposals, as and bug reports must provide a minimal context to understand and reproduce the idea. Currently i have some doubts about the idea with signals, but when i read this examples, i just confirm my assumption that proposal created by author who don't have enough experience of use javascript for enterprise, because of use an overcomplicated constructions.
If you want attention to your proposal, then simplify your code as much as possible, because even this small thing shows me that author don't know how actually programmers uses javascript and author just want to introduce one more thing that will never used by most of developers.
Simplify code in examples. Replace code like
const isEven = () => (counter & 1) == 0;to something likeconst isEven = () => (counter % 2) == 0;When i read this example, i feel straightforward overengineering and even don't want to read description.
Proposals, as and bug reports must provide a minimal context to understand and reproduce the idea. Currently i have some doubts about the idea with signals, but when i read this examples, i just confirm my assumption that proposal created by author who don't have enough experience of use javascript for enterprise, because of use an overcomplicated constructions.
If you want attention to your proposal, then simplify your code as much as possible, because even this small thing shows me that author don't know how actually programmers uses javascript and author just want to introduce one more thing that will never used by most of developers.