Angular v22 • Hacker News Board

Re: Angular v22

#81

Post by halflife » Thu, Jun 04, 2026, 4:39 PM UTC

zigzag312 wrote: post #79

halflife wrote: post #73

Earlier quoted context omitted.

A derived state is certainly reactive.

Of course you can have reactive state, your complaint however was: "The react in react stands for reactivity, however it is not." [because] "Its entire state management is not reactive" React is primarily an UI library, not full state management library. And its UI is reactive.

Agreed, the OP said that the r in rxjs stands for reactivity, so my point was the the names have little bearing on the actual design patterns achieved with the libs

Re: Angular v22

#82

Post by azangru » Thu, Jun 04, 2026, 5:03 PM UTC

halflife wrote: post #70

azangru wrote: post #67

Earlier quoted context omitted.

But why is push vs pull the definition of reactivity? I suppose we can say that there are different kinds of reactivity. Signals is one kind. Observables à la rxjs is a different kind (the whole model of programming with rxjs was referred to as "functional reactive programming"). Observables are push-based. Signals, as I heard, are a more complex primitive, which, under the hood, is push-pull. React's reactivity mode…

Maybe push pull wasn’t the best metaphor, but the point is that everything can be reactive, it only depends on how much boilerplate you need to write to achieve the desired result. Since react doesn’t have a true reactive model, you need to subscribe to changes manually (use effect) to create computations, while in signals it’s a primitive (computed). I actually created a lib that operates signals over reacts state m…

> you need to subscribe to changes manually (use effect) to create computations

How do you mean? Since the render function reruns during every update to state/props, derived/computed values can be calculated from the updated state/props during rendering.

Re: Angular v22

#83

Post by halflife » Thu, Jun 04, 2026, 7:00 PM UTC

azangru wrote: post #82

halflife wrote: post #70

Earlier quoted context omitted.

Maybe push pull wasn’t the best metaphor, but the point is that everything can be reactive, it only depends on how much boilerplate you need to write to achieve the desired result. Since react doesn’t have a true reactive model, you need to subscribe to changes manually (use effect) to create computations, while in signals it’s a primitive (computed). I actually created a lib that operates signals over reacts state m…

> you need to subscribe to changes manually (use effect) to create computations How do you mean? Since the render function reruns during every update to state/props, derived/computed values can be calculated from the updated state/props during rendering.

When all you need is a synchronous operations, yes. When it involves async, batching, buffering, and user input, it becomes much more complicated, and every step needs to be setup manually.

Re: Angular v22

#84

Post by zigzag312 » Thu, Jun 04, 2026, 7:56 PM UTC

halflife wrote: post #81

zigzag312 wrote: post #79

Earlier quoted context omitted.

Of course you can have reactive state, your complaint however was: "The react in react stands for reactivity, however it is not." [because] "Its entire state management is not reactive" React is primarily an UI library, not full state management library. And its UI is reactive.

Agreed, the OP said that the r in rxjs stands for reactivity, so my point was the the names have little bearing on the actual design patterns achieved with the libs

Ah, now I see what you meant.