I have been working with Node for about 3 years now and I have always used express. This video is all I needed to explore how all these functionalities have been abstracted from the actual core packages of Node. Thank you!
Bro the way you explain concepts makes me fall in love with technology, specifically backend tech. Throughout time I lost that passion I once had, and did it only just as a career. But I want to bring the same old passion back. Which you are helping me.
1:22 He's the one teaching yet says "you probably know this better than I do.". Nasser knows his audience. We have spent years with little idea of how little we knew.
Deno's core built-in listen and HTTP API is even more beautiful. It doesn't rely on callback-pattern, which can become very unwieldy if you haven't introduced a strategy to handle it early on in development but rather uses async iterators for iterating and gives you much more control over the control flow of your connection handlers. But I'd still want to use something a bit more high-level that allows me to define routes and handlers outside a loop and automatically filter and orchestrate requests based on pre-conditions. Working with a low-level API for application code is not feasible. They are great as building blocks for higher level concepts, though.
I'm completely new to node and to this channel, but after watching this video in its entirety, it seems like this guy needs to be putting out a node.js/express.js course, or maybe he has one already. He knows his stuff, and is very easy to understand.
akka-http has even more beautiful design. Atop of that, it has beautful routing declaration API. It is also type safe, which allows usage without reading any documentation.
Niceeeee Really missed those simple yet very insightful videos B.t.w - ate you using brave as your browser on your mac? Do you recommend? (Currently using chrome for the dev tools etc but I really want to switch for the sake of diversity)
Every time I look it up, basically no one thinks I should learn the HTTP module, and almost always say use express. I don’t really understand why many discourage just using HTTP. Can anyone clarify why this is?
I unironically make my backends with the http module. writing a stable login and signup system for instance only takes like half an hour if you have the experience
I was frustrated few weeks back coz I just knew that built-in node modules, like http is not supported in react-native. My project was suppose to call https backend with certificate authentication. I ended up binding native java code into react-native in order to do such simple task.
It's 2021 and this video is still teaching creating a new project using antiquated *"require"* statements instead of the standard *"import"* statements. The JS module ecosystem is a depressing mess because of obsolete stuff like this.
i love this kind of content, it's like having a cool older cousin of yours explaining stuff to you
Basics like this are often ignored! Thanks for the amazing content!!!
I know nothing of the NodeJS but boy have i learned something today...
I have been working with Node for about 3 years now and I have always used express. This video is all I needed to explore how all these functionalities have been abstracted from the actual core packages of Node. Thank you!
Bro the way you explain concepts makes me fall in love with technology, specifically backend tech. Throughout time I lost that passion I once had, and did it only just as a career. But I want to bring the same old passion back. Which you are helping me.
1:22
He's the one teaching yet says "you probably know this better than I do.". Nasser knows his audience. We have spent years with little idea of how little we knew.
Bro this one short video just put so many things together for me in my brain, I appreciate you!
I started to learn node.js a few days back and this video drops in. Thanks man!
All by design. Life is synchronicity.
Deno's core built-in listen and HTTP API is even more beautiful. It doesn't rely on callback-pattern, which can become very unwieldy if you haven't introduced a strategy to handle it early on in development but rather uses async iterators for iterating and gives you much more control over the control flow of your connection handlers.
But I'd still want to use something a bit more high-level that allows me to define routes and handlers outside a loop and automatically filter and orchestrate requests based on pre-conditions. Working with a low-level API for application code is not feasible. They are great as building blocks for higher level concepts, though.
Thank you Hussein. Keep up with this kind of Basic content, love it!
It brings more clarity about what I'm doing, i like these sessions..
Everyone has their unique way of teaching, so we get to learn new perspectives and gain deeper insights.
What an awesome video with very good explanations and under the hood researching, great job!
This is awesome. I started with Node through Express, then Fastify. Never really dived into this part
quality content, please keep this coming.
I'm completely new to node and to this channel, but after watching this video in its entirety, it seems like this guy needs to be putting out a node.js/express.js course, or maybe he has one already. He knows his stuff, and is very easy to understand.
Great video which shows in practice what happens under the hood. Keep it up Hussein!
akka-http has even more beautiful design. Atop of that, it has beautful routing declaration API. It is also type safe, which allows usage without reading any documentation.
never touched express or similar
I do like how intuitive the built in modules can be
Awesome man, I doesn't know those details about Node.js. Now go deep down to understand how these things works under the hood
This is a joy to watch
Niceeeee
Really missed those simple yet very insightful videos
B.t.w - ate you using brave as your browser on your mac?
Do you recommend? (Currently using chrome for the dev tools etc but I really want to switch for the sake of diversity)
Every time I look it up, basically no one thinks I should learn the HTTP module, and almost always say use express. I don’t really understand why many discourage just using HTTP. Can anyone clarify why this is?
This is such a good explanation of this simple concept. Thanks for the amazing video. And please do make a video on express also.
how does vs code debugger open when you run curl in the terminal
Love this type of content. Looking forward to see about QUIC as it's built in nodejs as well
Best video. Please keep doing stuff like this
You talk to curl like to a dog: "Look at you! Good Job!" :D
Good boy! 😂
Awesome thank you sir ❤️☺️
What advantages does Brave have over the other browser?
I never knew how to use break points until today lol
I unironically make my backends with the http module. writing a stable login and signup system for instance only takes like half an hour if you have the experience
How could an HTTP server serve a TCP request shown using telnet?
Because HTTP 1 and 2 are built upon TCP.
It is indeed beautiful, the explanation, I mean. haha
AMAZING CONTENT!
If client connects through different browser tabs,
Will client ports be different ?
dope video, great job, keep it up!
Why was connection.remotePort not 8080?
Great stuff
nice!
Thanks
I have built this dark mode in node docs :)
Nobody:
Fathers at Texas after the new law: 6:02
Cool stuff
I was frustrated few weeks back coz I just knew that built-in node modules, like http is not supported in react-native.
My project was suppose to call https backend with certificate authentication.
I ended up binding native java code into react-native in order to do such simple task.
I was today years old when I learnt about vscode debug mode. 🤣🤣
x 1.25 is the perfect playback speed for this video
Port ATAT... from StarWars??? Yeah, I just figured it out.
I'm a goose
wait until u try golang s http package
You sound a little drunk .. XD
First comment haha 👋
It's 2021 and this video is still teaching creating a new project using antiquated *"require"* statements instead of the standard *"import"* statements. The JS module ecosystem is a depressing mess because of obsolete stuff like this.
0:19 You said "so what I wanna do today is" twice
you should go work for the cia
@@felleg4737 😂
No, it's not. It's really really really not. For a tiny project (
lol, dude chill out.
@@calimio6 make a point or leave