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

[@MrAaronBlues]

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 :)

[@gustavcoetzee5018]

working with nest for more than a year now, what a cool talk, I can feel my heart beating faster as he explains it

[@Holdino_]

I'm in love with NestJS!

[@avimehenwal]

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

[@MojoRisingX]

Great talk! Love NestJS!

[@user-fw7ho5pj2i]

Watched this to study nestjs fundamentals. Crazy experience

[@muhammadtanveer286]

I'm in love with NestJS!,its amazing .

[@giorgimerabishvili8194]

Wow, this dude is a legend!

[@8eck]

Whoa look at the back of his notebook, this guy sure loves stickers :D

[@franciscokloganb]

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]

Why compromise when you have svelte?

[@MarcoSync]

NestJS Rules! s2

[@TiagoDark]

NestJS ftw

[@shy-soonyubing]

I'd like to know why nest.js strictly applies to Isolation of modules

[@name1483]

Those shorts caught me off guard

[@nikosc]

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]

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]

@@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.

[@jhonysou]

#LoveNestJS

[@boot-strapper]

this guy's glasses detract from his credibility

[@ricko13]

React fans hating Angular but loving Nestjs... I'm like WTF ???

[@eeebeltran5445]

Because Angular sucks but Nestjs doesn't