2024-06-07
1748
#angular
Lewis Cianci
191569
109
Jun 7, 2024 ⋅ 6 min read

Signals vs. ngOnChanges for better Angular state management

Lewis Cianci I'm a passionate mobile-first developer, and I've been making apps with Flutter since it first released. I also use ASP.NET 5 for web. Given the chance, I'll talk to you for far too long about why I love Flutter so much.

Recent posts:

Fix over-caching with dynamic IO caching in Next.js 15

Next.js 15 caching overhaul: Fix overcaching with Dynamic IO and the use cache directive.

David Omotayo
Aug 6, 2025 ⋅ 10 min read
LLMs are facing a QA crisis here’s how we could solve it

LLMs are facing a QA crisis: Here’s how we could solve it

LLM QA isn’t just a tooling gap — it’s a fundamental shift in how we think about software reliability.

Rosario De Chiara
Aug 4, 2025 ⋅ 7 min read

Windsurf vs. Cursor: When to choose the challenger

Windsurf AI brings agentic coding and terminal control right into your IDE. We compare it to Cursor, explore its features, and build a real frontend project.

Chizaram Ken
Jul 31, 2025 ⋅ 9 min read

The CSS if() function: Conditional styling will never be the same

The CSS Working Group has approved the if() function for development, a feature that promises to bring true conditional styling directly to our stylesheets.

Ikeh Akinyemi
Jul 30, 2025 ⋅ 12 min read
View all posts

2 Replies to "Signals vs. ngOnChanges for better Angular state management"

  1. Very interesting and nicely written article, thanks. Maybe you could post the whole component code on the end of the post? I am not quite sure where priceDifferences is defined – is it a function within the component? Or maybe, you not being very clear on this point, forces me to try it immidiately and I’ll remember your article better.

  2. Interesting post and nice comparison trick, thank you !
    I’m new to signal and I was wondering what ensures that the computed property executes before the effect ?

Leave a Reply