Makes zero sense to have signals natively in js. Why don’t there libraries just use a common library of the wanna “share” signals between them?
@GottZ3 ай бұрын
it makes total sense because native implementations can have higher garbage collection optimizations than library's in JavaScript land.
@zombiefacesupreme3 ай бұрын
This is exactly like promises. Everyone said "why add them to the language, we can just use bluebird/Q/etc.". Luckily, they were ignored, and the tooling around promises is much better. We have a standard primitive, and everyone is happy except some monad purists. People just hate change. When literally dozens of libraries have all converged on a similar reactivity model, it makes sense to codify it into the language so that people can stop wasting their life with duplicate workloads. You'll be able to use libraries in concert without worrying about conversion, and diagnostic tooling will be built into the browser. Everyone wins.