So often I see people struggling with missing imports and having no idea what the errors they are getting mean.

Looking forward to selectorless in 2025! It’ll remove this entire set of errors for standalone components and reduce boilerplate.

I feel like we need a simple authoring format, if you believe the existing format is good then you can stick to it, because Angular team not have mentioned that they are deprecating the current template format. Same thing happened to React also they still support class based components FYI.

Potentially. There are always tradeoffs.

This is why designing an authoring format requires very wide view, trying out many different things and several iterations. Plus careful evaluation of pros and cons.

Most importantly: lots of data-driven decisions and user testing in real-life setting.

Some issues with the current template format:
- Inline components are rarely used by most devs.
- External templates often lead to bloated HTML files (100+ LOC).
- Developers tend to avoid splitting components due to the overhead of creating multiple files.

This is my current exp as a lead Ang dev.