Community members have voiced uncertainty over the Angular team’s investigation into new authoring formats, worried that the effort may be surface-level only. During ng-Poland, the team outlined several motivations for the prospective shift, such as the significant amount of time needed to adjust TypeScript features for use in templates.
The recent revelation that the Angular team is investigating potential new authoring formats has generated considerable confusion across the developer community. With scarce initial explanations, many developers found themselves wondering why these changes were necessary, and some even perceived them as superficial, which predictably led to frustration.
Last week, ng-Poland, the largest Angular conference of the year, concluded. Four Angular team members attended, offering some much-needed clarification.
Alex Rickabaugh, the framework lead at Angular, pointed out that the TypeScript inside Angular templates isn’t real TypeScript—it merely mimics it—so any new feature demands its own dedicated implementation. For example, Matthieu Riegler had to invest substantial effort merely to support the typeof operator within templates.
feat(compiler): add support for the `typeof` keyword in template expressions
#58183
This commit adds the support for typeof in template expressions like interpolations, bindings, control flow blocks etc.
This raises a critical question for the community:
Should the Angular team keep reimplementing TypeScript features within templates, or would it be better for them to focus elsewhere, even if that requires us to adjust to a new authoring format?
Pawel Koszlowski, a member of the Angular team, also provided insights into the ongoing "signalization" efforts. They are looking to incorporate Signals into forms, working towards a consistent "Signal Form". Also on the horizon are Signals for the router, alongside a potential httpResource that could serve as an alternative to HttpClient.
You can find the slides at
ng-poland 2024 [public slides] - Google Slides
docs.google.com
That wraps it up for this week. Catch you in the upcoming installment!