51–60 of 84 posts
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.
Signals and signal stores make it very easy.
Did the whole coding by hand, no ai coding tools too.
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?
Seems like Angular has gotten better since v2 (my last experience). Has anyone done a modern Angular vs. React comparison that's not an AI slop article? I'm also curious if it's "simple made easy" for performant applications. React is arguably "simple made hard", but there are notable, highly performant applications written with it (Linear comes to mind).
I only touch it when doing projects like Sitecore, Contentful, Sanity, and co, where React/Next.js are the official extension points.
So many hooks, use "this" and "that".
Earlier quoted context omitted.
Each one of these solves a different problem. Promised - async Observables - streams Signals - reactivity
In theory that’s true (although observables are for reactivity too), but Angular uses observables for its http library and http requests are very much not streams. It’s one of the main downsides of working with Angular, the http library is mediocre and does come with the added overhead and complexity that rxjs brings. Until this release (if you only use stable features) using forms meant dealing with observables too,…
Regarding angular I agree, rxjs was a bad choice for data management, and before signals arrived I abandoned rxjs in favor of mobx in my angular projects. However you could roll your own http client, we used axios, and using DI it’s a drop in replacement.
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
explain your use case, I always wonder what kind of scenarios people do have, it is something easily solved? it is complicated? what is stopping you?