New Image Directives in Angular v15

In Angular v15 the image directive is now stable and you can use it in applications with standalone components and in applications with NgModules. Watch this video to see how to automate the generation of the image srcset, use the experimental fill mode, and other capabilities that ensure images exhibit optimal loading behavior.
Speaker: Alex Castle
Watch more from the Angular v15 Launch Event → goo.gle/Angula...
Subscribe to Angular → goo.gle/Angular
Angular Twitter → / angular
#Angular #Developer

[@adriensaulnier2270]

Hi, nice job, ty :)
1) Should we include the directive on all element ?
2) Should we include the directive if our loads an svg ?
Thank you !

[@aakash261]

That's a cool features for IMG

[@projectAIIR]

Cool. Will want to give it a try on my apps

[@artemeelemann317]

Could be more informative with more examples of usage and resulting bundle
But thanks for the feature anyways

[@PeterMoueza]

0:15 Vitals optim 1:15 unknown width*height 1:30 LCP

[@todd2133]

Any one know how to use an image with @Input for a reusable card component?

[@samuelokeke8144]

You can project the image using ng-content in the AppCard component

[@coreyfloyd3600]

✔️ քʀօʍօֆʍ

[@pranupranav6279]

React is way better than Angular.

[@dimitritsikaridze6220]

what's the point of this comment

[@pranupranav6279]

@@dimitritsikaridze6220 I hate angular.🤣

[@dimitritsikaridze6220]

@@pranupranav6279 have you ever used it? which part of the framework don't you like

[@pranupranav6279]

@@dimitritsikaridze6220 I have used it. No proper state management. Re Rendering is a problem, prop drilling is next level. No hooks. Hard to debug memory leaks and all. Many more.

[@dimitritsikaridze6220]

@@pranupranav6279 that comment tells me that your first framework was react and then you tried to apply its concepts to angular which doesn't work.
state management is lot easier in angular than in react with services and rxjs.
prop drilling is issue in react, in angular if you're passing value down to more than 2-3 components deep you're doing something wrong, services can solve this as well.
I don't understand what you mean by "no hooks" since hooks in react and lifecycle hooks in angular are somewhat different things.
and lastly for memory leaks if you understand how rxjs works and use async pipe properly you'll never have to deal with memory leaks ever again.