Quote · Syntax - Tasty Web Development Treats
1019: LGTM, Ship It: The AI Code Review Problem
Where this was said
The Angular vs. React Debate
At 28:30 · chapter starts 27:44
The question from Moto Moto Likes You frames a cultural clash familiar to anyone who has worked across JavaScript ecosystems: React developers reach for a library for everything, while Angular developers treat the framework as gospel and resist external dependencies. The questioner, a former React dev now on an Angular team, wonders if they should push harder to bring in more libraries. Scott, who stepped off the Angular bandwagon when Angular 2 dropped, admits he has sympathy for both sides — even on React projects, he often chose to build components himself because third-party dependencies carry real costs. But in the AI era, the calculus has shifted further toward doing it yourself: AI is increasingly good at writing precise, custom utilities that cover exactly your use case without excess baggage. Wes sides firmly with the Angular team, and offers a damning exhibit: Hammer.js, one of the two external libraries the team already uses, was last released 7 years ago. That's how dependency debt compounds — you bring in a touch library in 2017, it goes unmaintained, and now you're stuck maintaining it in 2024. The Angular instinct toward framework-native solutions, Wes argues, is exactly right.
Hammer.js, a touch-event library used by the Angular team in the episode's question, has not been updated in 7 years, illustrating the long-term risk of external dependencies.
