Building a platform: NestJS from the ground up | Kamil Myśliwiec | jsPoland 2018

Filmed at js-poland.pl 2018 on November 16 in Warsaw.
About Kamil Myśliwiec
NestJS Creator, Full-Stack Software Engineer
An enthusiastic software engineer who loves challenges, cutting-edge technologies, and programming at all. NestJS creator, open source contributor, a passionate developer on a mission to change the Node.js world.
/ kammysliwiec
www.goldenline.pl/kamil-mysli...
kamilmysliwiec.com/
nestjs.com/

[@AmnonSadeh]

As of Nov 2019 this video appears on the main page of the nestjs website (nestjs.com/)
This was my first visit and I came in order to learn more about it. Did I achieve my goal?
Not even the slightest.
WHY should I use this platform? What's wrong with just using Node? What PAIN is NestJS trying to solve for me?
I'm sure this is a useful video for someone who has already made a few steps with this platform, but for someone who haven't heard about it until 1 hour ago?
Let's say you want to sell insulated coveralls to someone who is going on a ski vacation. Are you going to explain about the various buttons and pockets it has? The well designed zippers and their functionality? How well it connects to whatever gloves the person already has? No! You're going to tell them "this will keep your ass from freezing!"
Sorry, I'm sure Kamil engineered a great product, but THIS shouldn't be the first video on the site.

[@jsPolandConf]

A completely new workshop with Kamil Myśliwiec: ng-poland.pl/workshop-scalable-node-js-with-nest-js-master-class.html

[@kevinwaag9976]

I dont think i'll use it, reminds me too much of java

[@nickjunes]

If all you know is Java then you want everything to look like Java. I personally like JavaScript and find no reason to reformat it and shoehorn it into object oriented style.

[@DaCurse0]

OO is a core part of JS though, I don't think it's shoehorning, it's just using OO. That's whats nice about JS, you have lots of freedom. You can write it functional, OO-style, imperative, etc.

[@Zeeno]

@@DaCurse0 OO design is littered with issues. It's generally good when working with actual objects (eg when defining database models. That annotation works pretty nicely) beyond that, writing js in a functional manner is a lot neater with way less boiler plate in my opinion

[@DaCurse0]

@@Zeeno The main benefit with OO in my opinion is that it lets you encapsulate mutable state, which is way cleaner than say, working with global variables.

[@nickjunes]

@avfr there's a lot more in the world than spaghetti and oop.