Kamil Myśliwiec - Revealing framework fundamentals: NestJS behind the curtain
Ближайшая конференция - HolyJS 2024 Autumn, 7 ноября (online), 14-15 ноября (Санкт-Петербург + трансляция).
Подробности и билеты: jrg.su/K18Cxd
- -
. . Kamil - автор NestJS. Он расскажет про подкапотные вещи и основные концепции NestJS. Что может быть интереснее, чем детальный разбор интересной и популярной технологии от её автора?
When Node.js came up for the first time, it was considered as an outstanding revolution. After few years, the platform evolved substantially, albeit tooling wasn't good enough to compete with mature technologies from other languages. Nest has been formed to bring hope back by applying modern techniques and design patterns to the Node.js world. In this talk, Kamil will introduce Nest to you as well as show internals of the framework's key features.
Пікірлер: 19
By far the best framework for node
When I was introduced to NestJS in Feb 2020, it was around 12k to 15k or 20k Github stars. I actually I don't remember well! I am very glad that the core team and community contributed to build the project. Today NestJS has 37k stars. Let's keep it up!
None of the many framework vids I've seen clearly demonstrate 1) the value of frameworks in general with relevant examples 2) the reasons why any particular framework is better for this or that I understand the value of reusable building blocks, but it seems the time spent becoming fluent in these products is better spent on developing great vanilla skills? If I learn to create a quality login module in js all by myself, I'll know exactly how it works, and it'll be as reusable as any framework module? Maybe I'm just a control freak...
@user-vw9qj8el4q
2 жыл бұрын
It is a waste of time to try to implement your own login module when where is a lot of such modules being maintained by open source teams
@gubocci
2 жыл бұрын
Control freak... Or just too lazy to learn new things? ;)
What's the purpose to use a function to instead a class for controller?
@damiangilz
4 жыл бұрын
The same way you don't use a class to make Express routes, it's not needed nor you can extend anything to it since the underlying frameworks don't use them.
Just too unnecessarily complicated Monolithic framework with steep learning curve. If you would need such complexity, would rather use spring boot or .net core than javascript. Unit testing for instance is so hard with all modules , etc. Express with typescript is clearly more simple and easier.
@SitSkw
3 жыл бұрын
Woow I'v got such a different opinion :) I've started with Node + Express and made few projects with it. Now I'm finishing my first bigger Nest project and I'm certain I will not go back to express again if I will not need to. Working with Nest for me was a pleasure. But thats only my opinion. :)
@khaled_osman
3 жыл бұрын
@@SitSkw Neither classes nor decorators are really part of javascript, I also have mixed feelings about it, it makes difficult things easy and easy things difficult, you have to create 5 classes/files for something that you can do in a 3-line request handling function in plain express. it feels more for java or c# developers who want to use their familiar complex systems resulting from the horrors of class oriented programming and don't want to bother to learn proper javascript development
@brucewayne2480
2 жыл бұрын
@@khaled_osman Java or C# developers are not doing complex systems for fun, because softwares are complex, specially apps with a lot of functionalities , if you're not structuring your code and try to apply the best practices you won't be able to maintain it or even debug it , other developers wont understand it too
@khaled_osman
2 жыл бұрын
@@brucewayne2480 they kinda are, it's all workarounds for class oriented programming, if they can structure their code as a bunch of single responsibility functions and split them across enough files in JavaScript land things would be much easier
@brucewayne2480
2 жыл бұрын
@@khaled_osman I'm a js dev , and I said the same thing few years ago , JS is a lot simpler. But the more functionalties you add to your app , the more an architecture and typed language become a necessity. When you have 10 endpoints that can change the same entity and modify it in the controller , if you change one property , it will become a nightmare
I've migrated 3 of my services to NestJS so far. It's the best framework for Node at the moment. Love it.
We can't wait any longer for nest to become popular
Great talk!. Thanks
I wish Kamil never made this talk, tired to fight crazy rush to wrap all inside one big base "CRUD" controller / service.