Signals for JavaScript Proposal - Full Video! 🥳🔥 Alex Rickabuagh & Ben Lesh | TechStackNation.com!

🤩 Link to Alex's HackMD page: hackmd.io/UK0DmHnRTr6A0QyQ1OHjrw
Did you know? These chats are done live in a cozy google meet and you're invited! Join our Experts Space to participate in calls like this live to ask questions, offer feedback, and network with leading tech experts! 🔥
Found this video helpful? Make sure to click the Like 👍 button if you want to see more videos like this.
👉 techstacknation.com/ is the place for innovative developers and software architects to hang out together and compare notes!
Big thanks to our community sponsor, AG Grid! ❤️
#angular #react #vue #javascript #typescript #devops #enterprisearchitect

[@armynyus9123]

My Hero.

[@krisnrg]

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?

[@GottZ]

it makes total sense because native implementations can have higher garbage collection optimizations than library's in JavaScript land.

[@zombiefacesupreme]

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.

[@LarsRyeJeppesen]

It makes very good sense