The "Unpopular Opinion"

Stop using NgModules. Period. The "old guard" is still clinging to AppModule out of a sense of comfort, but your legacy architecture is actively sabotaging your application's future. If you haven't moved to a 100% Standalone architecture yet, you aren't just staying organized—you’re paying a "technical debt tax" every single day. Here is why it’s time to hit delete: Build Speed & Tree-Shaking: Modules create artificial dependency buckets that bloat your bundles; Standalone components allow the compiler to aggressively prune what you don't need. The 20% Rule: Teams moving to full Standalone are seeing up to 20% faster CI/CD pipelines because the dependency graph is finally flat and predictable. Developer Velocity: Stop jumping between three files just to add one component; Standalone turns the friction of "Angular overhead" into the streamlined experience of modern web dev. I know, migration is a "pain in the service layer," but the trade-off for a leaner, faster, and more scalable code