Demystifying Dependency Injection: Angular vs NestJS - Kamil Mysliwiec | NG-DE 2019
Dependency Injection framework is a core and inherent feature of both Nest and Angular. DI simplifies creating scalable, testable, and maintainable applications by giving us flexible and efficient abstractions. However, did we ever think how this mechanism works underneath? In this talk, we’ll compare how Nest and Angular DI systems differ from each other as well as dive into the basics of the metadata reflection API in TypeScript.
Kamil Mysliwiec: ng-de.org/speakers/kamil-mysl...
Follow us on twitter / ngdeconf
Official Website: ng-de.org/
Video Production: medienkompetent.com
Пікірлер: 25
It's been the 50th time I'm listening to this video, every time I understand 1% better DI in Nest but I'm far from understanding it well yet, 50% actually :)
I'm in love with NestJS!
working with nest for more than a year now, what a cool talk, I can feel my heart beating faster as he explains it
Great talk! Love NestJS!
I'm in love with NestJS!,its amazing .
I am build a new product using nestjs .... This video is god-tier explainer on how nestjs DI works. Learnt a lot Thankyou so much for sharing
Wow, this dude is a legend!
Watched this to study nestjs fundamentals. Crazy experience
I like his glasses. Moreover, I must say I love the principles of Nest.js on the backend, but honestly, I think Angular is worse than React. Vue makes a good compromise between freedom and code predictability. :)
@kiranojha8811
2 жыл бұрын
Why compromise when you have svelte?
NestJS Rules! s2
Whoa look at the back of his notebook, this guy sure loves stickers :D
NestJS ftw
To save some time for some people, Nest.js's DI framework does not offer a solution for Interfaces and Generics to be used as providers
@finally_code
4 жыл бұрын
why would you want that? You can use normal inheritance for an Interface and a generic type declaration is just a type construct that can't be passed around outside of a type definition.
@sociocritical
4 жыл бұрын
@@finally_code Yes I also dont really see a reason for that. Even if you wanted to switch between providers which implement a specific interface after init you could just assign the initially injected provider to the interface in the constructor. If you want to choose before init you can just use a custom provider factory, which doesn't need type information due to the custom token.
@renatosanhueza890
Жыл бұрын
thanks for the warning. I am dying looking for a solution for this crap.
Those shorts caught me off guard
I'd like to know why nest.js strictly applies to Isolation of modules
#LoveNestJS
React fans hating Angular but loving Nestjs... I'm like WTF ???
@eeebeltran5445
2 жыл бұрын
Because Angular sucks but Nestjs doesn't
this guy's glasses detract from his credibility