What's New in Angular v15, by Minko Gechev

preview_player
Показать описание
In this talk, you'll learn about the advancements in developer experience Angular has made over the past year. In the first part of the session, you'll learn about improvements in the component authoring format, e2e testing, and performance. In the second part, we'll cover the advancements in the debugging experience and how Angular and Chrome DevTools evolved stack traces for web developers.

Speaker: Minko Gechev,
Product & DevRel lead for Angular at Google

#JavaScriptDay2022

–––

🔗 Browse our resources 🔗

Check out WebStorm, a JavaScript IDE by JetBrains, and get a 30-day free trial:

⭐️ Keep in touch ⭐️

JetBrains on Twitter:

WebStorm on Twitter:
Рекомендации по теме
Комментарии
Автор

in my opinion classes and templates are Angular. it's one of the main reason I use Angular. Please don't make Angular syntax like React or Vue. Innovation is great, but it becomes pointless when fixing something that works. I am grateful to the Angular team for creating and maintaining Angular. Every Angular release I am always happy, for new improvements, new features and the tooling that makes it easy to upgrade, thank you.

sivuyilemagutywa
Автор

Im thrilled that Material got a update. I felt like I was always fighting with its styling.

vanmuscari
Автор

lazy routes look cool & elegant, seems interesting features are ahead.
ty, nice presentation as always 👌, modest and precise, with no marketing buzzwords like "supercharged" or "developer ergonomics"

matijacvrk
Автор

I think that the object Orientation (Class Based) of Angular is one of its Core features as it makes it less mentally challenging to build High Quality Full Stack Applications. It also seems to me that this is the primary Use Case in business as is. Using Angular as the Frontend for Enterprise Applications where the Backend often Comes in C#/Java.
The Concepts and Best Practises are not Far from what they are in those Backend Enterprise Languages.
I love what you have done with Angular 15 and am curious for the future.
I think that this Concept in Angular should be kept in mind tho. The similarity of Design Principles and Best Practices to Design Driven Backend Technologies, is a great benefit none of the other Frameworks offer.
It's Easier to start with Vue for sure, but it is not very easy to understand how to cleanly structure a Vue Project from a experienced Backend Developer's Perspective.
Similar in React, even tho this technology is likely closer to home for functional Programmers, NodeJS Backend Devs and general experienced JS Devs.
Angular here fills the Spot missing, here we can use Design Principles also used in Backend Languages, to improve the base Design of our Frontend Application. I truly apreciate that.

bad-at-art-games
Автор

Are classes Angular? - Yes
Are template Angular? - Yes (They both give a nice way to separate the concerns. Makes the code well organized. Especially when you are working with a team with mixed technical expertise)

IMO .. Please dont use React Singling - They are not intuitive at all. I would rather go with the flutter approach of just simply using setState().

_dinesh
Автор

How to get the Single Component Build ?

denishpatel
Автор

Hi, thanks for the presentation.
I am working and making Angular apps since v2 and being the responsible for update Apps with it since with v5, A lot of improvements on the way of update the apps with new versions and since v9 a much better performance in dev and builds speed.

Until version 13 the syntax in ts and template engine has been stable, what i dont want to see is something like react and vue has, which is two ways to write apps ( functional components and composition) where you are introducing standalone components.

What it is not very clear with standalone components in your docs and videos is if we still can separate the style and template of the component in separate files ( css and html), i had not yet time to try standalone comps and at my job still using v13, but should be clear,
if standalone components only means component without the need to assign to module were the rest is the same like separate css and template from the logic ( TS ).

About are Classes Angular?

I think a components not always need a logic / TS file, I recommend Angular to read what Aurelia did and still doing for v2 ( so called html only components) and even emberjs is thinking this way.

Another thing missing is choosing linter tool setup with Angular CLI.

jediampm
Автор

Did you mention that they got rid of environment files? You can still add them if you want. I think everyone is preferring to use continuos deployment settings to update api urls instead of having to do it at design time with angular buid

fav
Автор

I'm having trouble understanding some of the diction and unfortunately, adding closed captioning doesn't seem to help. Looks like it was autogenerated and it doesn't quite understand you either. Specifically when you start the section around ng build, there are words I can't understand. You might have said ng build is using es built? There were some other acronyms that you said as well. Suggest adding a little more content to the slides for when you say something like ng which is not a standard English word but is sort of a made up Angular or Javascript centric word the auto closed captioning system will not pick up on.

mikesage
Автор

kinda regretful if angular bring preact signal concept if there is rxangular available

sulaimantriarjo
Автор

why painting yourself in a corner by using angular, vue or react?
or: when the framework is determining the architecture the industry isn't mature

BrunoJennrich
Автор

I will add also a plead. Please do not change templates and classes in angular. This is the best thing in angular and I do not want to write react in angular. React and Vue just sucks.

pawepolak
Автор

The debugging improvement is a welcomed feature. Angular is a joke of a framework that will continue to break, these clowns keep questioning and changes the core. Is class Angular, is template Angular....Is Angualr Angualr? They created NgModule when JS module could have been used and later decided it's not needed. Why wouldn't you just make all modules lazy loaded by default? then as the page loads, it fetches the code and resources need on "demand". Nope, they needed to over-engineer and add super ugly boiler plate code, to routing. You know what is not Angualr RxJS, Streams, Observals. These things alone have resulted in over-engineer crappy, abstract hard to read and maintain code with dependences breaking. Ngrx is an over-engineer mound of dung, just to be able to have a global store to get and fetch value, only 2 simple operation are
needed. Again it's over-engineed with reducers, actions, selectors, effects, component store? WTF.

Angular Material should not be a part of Angular. We have CSS so leave it to someone else to create a CSS library, it's just bloat very few want to use professionally. Also bugs go unfixed, so for CSS markup this is just stupid to tightly couple it to code not under your control. You can make your own CSS components, you already got Angular + CSS.

Also their reference docs are incomplete, they haven't been worked on forever, maybe fully document it first?

Answering: Is Angular Angular? Nope! This is why they keep breaking the code! Zero backward compatibility, maintanance nightmare.

RajinderYadav
Автор

Angular lost it's battle with React and Vue. Why would anyone choose Angular over those two?

dmitriyobidin