3 ms·

how so?

• webprofusion 3y ago
  https://knockoutjs.com/examples/helloWorld.html https://knockoutjs.com/examples/helloWorld.html Signals are very, very, similar to knockout observables. (Note that Knockout observables are very different to Rx/Reactive observables).
• steve_adams_86 3y ago
  Though the idea of signals has been written about and used in computing for decades, knockout was the first frontend framework to implement them in a form we’d recognize as signals today. I think that’s why people are getting worked up about angular using signals. Claiming we’re circling back to knockout makes no sense though. Signals are sort of a primitive for modelling solutions; they aren’t the solution. The fastest tools for UI development are presently using signals to solve performance issues such as Solid, Qwik, or even Leptos which uses WASM and still outperforms React. React maintainers have said that signals could even be used in react eventually, though they don’t want it to be a surfaced tool that you have an API for. Instead it would be generated with a compile step. Regardless, we’re not headed back to knockout days and signals are not an archaic solution to a specific problem that we already have better tools for — there’s still plenty to revisit and explore to get better performance.