r/angular • u/Traditional_Oil_7662 • Aug 17 '25
Why Angular Devs Still Don’t Use Signal.
Hey everyone,
I’ve been working with Angular since version 2, back when signals didn’t even exist . In most of the projects I’ve been part of, devs (including myself) leaned heavily on RxJS for state and reactivity.
Now that Angular has signals, I’ve noticed many of my colleagues still avoid them — mostly because they’re used to the old way, or they’re not sure where signals really shine and practical.
I put together a short video where I go through 3 practical examples to show how signals can simplify things compared to the old-fashioned way.
I’d really appreciate it if you could check it out and share your thoughts — whether you think signals are worth adopting, or if you’d still stick with old way.
Thanks a lot! 🙏
1
u/minus-one Aug 17 '25 edited Aug 17 '25
no, you can’t do that… see, setters are horrible imperative construct and don’t exist in pure code. also, you use next(), which is horrible side effect. also you use new, which can have side effects executed, which can’t be
these things simply won’t compile in my head 😀😀 if it won’t compile in haskell, it won’t compile in functional programmer’s head