Jeremy Elbourne, an Angular team member, improvised and live-coded the board game "Boogle". Joey Perrott revealed some insights about Angular development at Google. And we have got two interesting articles about unit testing and Three.js in Angular.
Building Games and Q/A with the Angular team
NgGaming used to be a monthly session on YouTube where participants could ask questions, and members of the Angular core team, mostly Jeremy Elbourne and Mark Thompson, responded.
The format changed a little bit. The focus is now more on Jeremy live-coding some popular board games.
Jeremy has an improvised style, which means we see him struggling, as we all do when we write code.
And this is what sets it apart from other sessions, where presenters rehearsed everything to perfection.
You can see and learn how Jeremy approaches a problem and how he tries to solve it.
A View From the Inside of the Angular Team with Joey Perrott
Joey Perrott, a member of the Angular team, participated in the latest episode of "The Angular Plus Show", a podcast. In the first part of the episode, he gave some insider information.
Google has an internal repository but syncs it with the official one on GitHub. So this means that Google has no Angular internal stuff, which they hide from us.
Three teams are mainly responsible for Angular: The framework team, the tooling (Angular CLI), and the components, which is Angular material.
They also talked about Bazel, Google's open source build orchestration tool. It can build artifacts quickly but is also very time-consuming, i.e., you have to write many build files.
Articles
Renan Ferro: Understanding and Implementing Three.js with Angular and creating a 3D Animation
Renan Ferro wrote an article on integrating Three.js natively into an Angular application. Three.js is an abstraction library over WebGL, and you use it to generate 3D graphics in the browser. Natively means you don't need a glue library like ngx-three-js or something similar.
Quantarius Ray: Angular Testing: Unit Testing
Another article is from Quantarius Ray. He discusses the differences between unit and component tests and especially in which cases unit tests make sense. According to Quantarius, you test only a class in unit tests, and in component tests, you go via the DOM.
Spectator 12
NgNeat released with version 12 a new major of its popular testing library Spectator. It has Angular 14.2 as a minimum requirement.
Top comments (0)