During the Angular gaming broadcast, Mark and Jeremy talked through standalone components, change-detection mechanics, the Signals system, and the inject function for DI. Minko Gechev joined Angular+. Survey responses indicated that developer contentment has risen, yet certain shortcomings remain to be tackled.
Q&A with the Angular Team
During our monthly Angular gaming session, Mark and Jeremy from the Angular team joined us to respond to audience queries and share valuable insights. Below are the standout takeaways from the discussion.
Jeremy highlighted that Angular's direction centers on standalone components as the primary approach. At the same time, NgModules remain in place, since a substantial number of applications—such as those built with Angular Material—depend on them extensively.
It’s easy to conflate zone.js with change detection, but they aren’t the same mechanism. Change detection, which handles DOM updates, remains intact in a Signals-based world. Both zone.js and Signals serve as triggers for change detection. With Signal components, expected in Angular 17, change detection is set to become more fine-grained, or as they put it, more efficient.
Signals won’t displace state management libraries such as NgRx or RxAngular. The Angular team acknowledges these libraries’ necessity and works closely with their maintainers to ensure smooth compatibility and ongoing development.
For dependency injection, the guidance is clear: choose the inject function over the constructor. A future automatic migration could even steer codebases in that direction.
The reasoning centers on decorator standardization. Angular prefers standardized decorators over experimental ones. Constructor-based injection relies on parameter decorators, which lack standardization and create uncertainty. The inject function sidesteps these concerns by working with a plain object literal.
Angular Plus Show with Minko Gechev
Minko Gechev was a guest on the Angular+ show, a podcast hosted by three people. The conversation covered the Angular 16 release, spotlighting its two headline features: Signals and hydration. While there were no big surprises, the episode delivered a thorough walkthrough, including lively discussions about RxJs's future and the trade-offs between Standalone components and NgModules. With a relaxed, amiable vibe, the episode proved both pleasant and insightful.
S5 E13 | Discussing Angular 16 and Beyond with Minko Gechev
When Angular 16 dropped on May 3rd, so did a lot of jaws. It's hard to believe that the Angular team was able to pack so much into a single release. In this epi
spreaker.com
Angular Developer Survey Results
Minko Gechev, moreover, presented the survey's outcomes. The framework's satisfaction rating saw an uptick, moving from 85% to 89%. Among the areas where the community sees room for growth are docs, the authoring format, and how quickly the app loads on the first pass.
Angular Developer Survey 2022 Results Summary | by Minko Gechev | Angular Blog
The Angular team is evidence driven — we collect feedback from developers to decide what should be part of our roadmap. We get data from…
blog.angular.dev