Do any die-hard Angular devs understand why they are pushing us into standalone? [closed]

I can’t be the only one who sees that standalone is not an efficient way to code a large scale application?

• Having to list every dependency in every component rather than just once in a module?
• Losing the ability to group and manage components in a organised way?
• Losing readability and decipherability when handing over an app to the next developer?

These are just a few of the pitfalls I see.

I can understand why they added it:

• Easier for newbies
• More like react for converts
• Useful when you want to create a small app, with 1 component or very few

But react sucks, that’s why I am an angular dev. And many other die hard devs already exist so I cannot understand why in angular 20 they would enforce standalone: true as the default, and they have deprecated bootstrapModule in favour of bootstrapApplication which doesn’t accept a module.

It’s one thing to add it as an option. But I don’t understand why it’s clearly becoming the only option. Can anyone help me understand? What am I missing? What’s so great about having an application with 250 components and having to list them all 250 times in component imports?

I know, I know, I can just list them once ina master file and import that, but we already had that setup - it was called modules!

Continue reading...