News for hackers. Stuff that matters.
Re:A proposal to add signals to JavaScript by flohofwoe on Monday April 01, 2024 @05:32AM (#39892254)
> ...but since signals are something that is used in a variety of frameworks...

...common usage is not really a justification for putting it into the language standard though. Glancing over the readme I'm not seeing anything that would require changes to the language syntax and can't be implemented in a regular 3rd-party library.

In a couple of years, another fancy technique will make the rounds and make signals look stupid, and then we are left with more legacy baggage in the language that can't be removed because of backwards compatibility (let C++ be a warning).

Re:A proposal to add signals to JavaScript by Zababa on Monday April 01, 2024 @05:43AM (#39892320)
From what I understand, a few/many of the big frameworks are converging on signals, and another commenter said that Qt had signals in the 90s https://news.ycombinator.com/item?id=39891883. I understand your worries, and I would appreciate some wisdom from non-JS UI people, espcially if they have 20+ years of experience with them.
Re:A proposal to add signals to JavaScript by Offler on Monday April 01, 2024 @07:25AM (#39892955)
Every framework is moving to signals, apart from React and I'd say if this became a standard even they will. This is like Promise. It's a sensible shared concept.