Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Angular v22

blog.angular.dev

Post reply on HN
Print view View original

61–70 of 84 posts

Re: Angular v22

#61

Post by merb »

zcdziura wrote: post #15
merb wrote: post #11

the biggest problem in angular is that it is so hard to use a custom toolchain, i.e. not their angular/cli product instead mix it with other stuff in lets say vite

What kinds of features or workflows are you missing that Angular's CLI doesn't cover? Or is it just that you're used to Vite (or something else) and wish you could use that instead of Angular's own tooling? I'm not on the Angular development team or anything, though I do use Angular at $DAY_JOB and I'm overall perfectly fine with the framework and its tooling. However, the grass might be greener elsewhere; I'm just n…

Mixing with existing code gradually migrating to and from angular

Re: Angular v22

#62

Post by smrtinsert »

A framework releasing an official MCP as well as making AI tooling a key offering is new to me and it immediately strikes me as absolutely necessary.

Re: Angular v22

#63

Post by azangru »

halflife wrote: post #59
azangru wrote: post #48

Earlier quoted context omitted.

> Observables - streams > Signals - reactivity The r in rx stands for reactive.

The react in react stands for reactivity, however it is not.

React reacts to changes in state or properties by automatically updating the UI. What's not reactive about that?

Re: Angular v22

#64

Post by halflife »

azangru wrote: post #63
halflife wrote: post #59

Earlier quoted context omitted.

The react in react stands for reactivity, however it is not.

React reacts to changes in state or properties by automatically updating the UI. What's not reactive about that?

Its entire state management is not reactive, it’s always on push, not pull. You always need to call setState to get render changes.

Re: Angular v22

#65

Post by HatchedLake721 »

darkteflon wrote: post #33
majora2007 wrote: post #25

Really excited for this. I've been dying to use signal-forms and resources since they were experimental. Once I got on the signal train, I could never go back and having to use RxJS for forms became a major pain point.

Could you say more about signals? Is it are all analogous to, say, game engine signals paradigms (eg Godot) - components at any depth emit signals and any other component can subscribe? Or something totally different?

https://github.com/tc39/proposal-signals

Re: Angular v22

#66

Post by HatchedLake721 »

etothet wrote: post #41

I haven't been involved in Angular for quite some time. As someone who uses other JavaScript frameworks (Vue, React, Svelte), what am I missing out on? I'd be curious to hear from people who would pick Angular over any of the other big frameworks.

Angular (and e.g. Ember) are the “Rails” of frontend frameworks.

React/Vue/Svelte are view libraries that give you more flexibility.

Angular gives you structure.

For large enterprise apps with many developers, consistency and standardization is often the main reason people choose it.

Re: Angular v22

#67

Post by azangru »

halflife wrote: post #64
azangru wrote: post #63

Earlier quoted context omitted.

React reacts to changes in state or properties by automatically updating the UI. What's not reactive about that?

Its entire state management is not reactive, it’s always on push, not pull. You always need to call setState to get render changes.

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 model may be crap; but this doesn't make it non-existent.

Re: Angular v22

#68

Post by NuclearPM »

sgt wrote: post #13
TheChaplain wrote: post #4

I like Angular, it feels a bit like Django. Easy to use with everything included.

Or I mean, you could just use Django (or some faster backend with templating and SSR). Using that with htmx you get the SPA experience and still without the madness of an actual rotten JS ecosystem.

What is the “I mean” for? Are you clarifying a comment you made earlier?

Re: Angular v22

#69

Post by majora2007 »

fsuts wrote: post #38

How does modern angular performance compare to the alternatives? Is it as fast?

What does "fast" even mean? I always see people talk about performance and wonder, what kind of applications are they building where they are seeing a massive gap in performance between frameworks?

I'm pretty sure in this late game, all the frameworks are more-or-less the same in terms of render performance. Angular has a lot of cool tricks (with these signals) that allow for only re-rending what changes.

Re: Angular v22

#70

Post by halflife »

azangru wrote: post #67
halflife wrote: post #64

Earlier quoted context omitted.

Its entire state management is not reactive, it’s always on push, not pull. You always need to call setState to get render changes.

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 management (https://roypeled.github.io/react-logic/), so I removed the boilerplate to create a true reactive system.

If you want, you can create reactive system just from JS primitives, using callbacks. But that doesn’t make JS reactive by nature.

Post reply on HN