Dmytro Mezhenskyi’s newest video takes aim at stale Angular misconceptions, shedding light on how far the framework has come. Matthieu Riegler unveiled fresh migration tooling for Angular 19, making the transition to the input function and signal queries smoother than before.
Common Angular Myths
Angular's rapid evolution brings a side effect: outdated facts often linger as half-truths. In a fresh video, Dmytro Mezhenskyi dissects prevalent Angular myths and clarifies what’s shifted in recent releases.
He targets fallacies such as Angular underperforming or its bundles always being bloated, while correcting the assumption about dirty marking failing to trigger change detection—a notion that's outdated now.
Long-time Angular developers could easily fall behind; revisiting past architectural choices might be in order.
Signal Input Migrators & Video
Over on the Angular 19 side, Matthieu Riegler of the Angular team has introduced a fresh migrator designed to swap out @Input() decorators for the newer input function used in property binding. Additionally, a separate migrator targets signal-based queries, including viewChild and contentChild.
These features are ready for experimentation right now with Angular’s latest release. Although they directly alter source code, running these migration scripts is straightforward and carries no risk.
And if you'd like to dig deeper into Signal Inputs ahead of the migration, Igor Sedov put out a video offering an in-depth walkthrough.