🔗State of Angular | March 2022
This event was co-hosted by This Dot Labs team members Rob Ocel, Software Architect and Engineering Lead, and Chris Trzesniewski, Senior Software Engineer.
If you would like to watch the full event, you can find the recording here: State of Angular | March 2022
What's new in the ecosystem? What will be included in the upcoming releases? What should we expect in Angular's future? These topics were discused by a featured panel:
- Mark Thompson, Developer Advocate, Google
- Alex Rickabaugh, Software Engineer, Google
- Madleina Scheidegger, Engineering Manager for Angular, Google.
Here are some of the key takeaways:
🔗What's new in Angular?
Since the launch of v13, the Angular Team has continued to improve and refine its features:
- Extended Diagnostics.
- Gave us better guidance and some more options to make sure that we can avoid some of the most common anti-patterns in Angular.
- Enhanced component a11y. 🔥
- Since the v13 launch, the Team has made a number of improvements regarding accesibility. For example, they did an audit of the components to make sure those components passed all standard accesibility checks. You can review them here: Accesibility Angular Improvements
- Typed forms. One of the most important changes introduced was the ability to check the form type and throw an error if the type is not properly set.
- Standalone components. They are still working on the implementation to make standalone components happen.
Other features in progress:
- CDK promoting to stable
- Embebbed view injector
Then, we had some time for a Q&A. The highlighted questions included:
🔗Angular Components are often hard for newcomers to understand. Standalone Components should help mitigate this. How will this new Component type ease the learning curve?
The team agreed that 'ng modules' are hard concepts for newcomers to learn, and they had many conversations about this opinion. 'ng modules' have more than one responsibility, and often these responsabilities have different scopes. They're tough to understand because they are doing different things in different places.
Standalone components enable developers to write Angular apps without writing any 'ng modules'. Devs will still be able to use 'ng modules', and they will have the ability to perform imports. However, they won't have to learn how 'ng modules' affect the app, and that will help simplify the learning process.
🔗SCAM Pattern, and how it is related to Standalone Components.
According to the team, using the SCAM pattern is the cleanest approach one can use, and Standalone components will be the SCAM pattern's next level.
🔗The team has successfully decreased the volume of tickets, issues on the backlog, and open PR's. How was the process for the team? What lessons has the team learned?
According to the team, this process has been tedious, but also rewarding. This year, the team wanted to make it easier for the community to provide feedback. For example, they created a process allowing community members to suggest a feature request, and let the community vote. If the request achieves a certain number of votes, it goes to a queue for the team to review and work on. This helps the team prioritize the most essential tickets and proposals.
The team is constantly monitoring these trends, evaluating them, and learning from them. While they want to advance the framework, they don't want do that at the expense of the experience of those who adopted a previous version of Angular. Therefore, if the team choses to include any transformative changes, they want to do it in a way that shepards all users to the updated versions.
Angular's outlook is overwhelmingly positive, and the community is growing. It is an exciting time to be an Angular developer, and there are some really exciting features coming down the pipe, so we are really excited to see what will come next.