Great video 🎉, I too just started to build with .dotnet web api after only ever using nodejs. It was overwhelming at first, especially when all the tutorials i watched had all the controller architecture, repository patterns, dtos, dependency injection and many more. But i feel a lot more comfortable with it now. I guess all that unopinionated express code was too hard to top😂. Although🤓, you don't need to install body-parser to intercept request json. The express library can do that already by using the express.json(). Keep up the good work.
There will be a lot of OOP and Interface gymnastics when the application gets bigger. Node will still be straight forward in my opinion focusing on business and productivity.
No need for bodyParser if you send the name in query params as you did to the c# app: var express = require('express'); var app = express(); app.get('/', function(req, res){ res.send('hello ' + req.query.name); }); app.listen(3000);
@@ajasshaffi5395 i figured it out... At the start go for nodejs like it would be little easy to understand the concepts of backend after that with time you can switch to .net if you want to... I'm working with nodejs right now 😊
Node ecosystem is garbage in my opinion. 4 years experience in js/ts and I have learnt multitude new orms, frameworks and other stuff that in c# got one solution that everyone use and that is first party supported. I started with c# just 3 weeks ago, transition was very easy. I will stay with it for a while. I want to finally learn patterns, better programing solutions and not damn orm or framework or validation library or other crap every project or two.
Not apples to apples comparison considering In GET, dotnet is sending plain html while node is sending json In POST, dotnet uses search params while node uses request body for sending data
Yesterday I've asked to ardalis compare his fast endpoints with nextjs? Some parts are answered here. Thx
Great video 🎉,
I too just started to build with .dotnet web api after only ever using nodejs. It was overwhelming at first, especially when all the tutorials i watched had all the controller architecture, repository patterns, dtos, dependency injection and many more. But i feel a lot more comfortable with it now. I guess all that unopinionated express code was too hard to top😂.
Although🤓, you don't need to install body-parser to intercept request json.
The express library can do that already by using the express.json().
Keep up the good work.
ප්ප්ප්
great comparison!
what dou you recommend between dot net core and django?
You don't need body parser to parse json in express. Express comes pre-built with express.json() middleware for parsing JSON.
It does not come with a parser its the headers that do the job for it
There will be a lot of OOP and Interface gymnastics when the application gets bigger. Node will still be straight forward in my opinion focusing on business and productivity.
Abstraction greatly helps the codebase as testable and loosely coupled.
😂😂😂😂😂😂
All my respect
No need for bodyParser if you send the name in query params as you did to the c# app:
var express = require('express');
var app = express();
app.get('/', function(req, res){
res.send('hello ' + req.query.name);
});
app.listen(3000);
How did I not subscribe to your channel
I'm to start my backend journey what should i choose .net or nodejs ?
Bro I am having the same confussion.
@@ajasshaffi5395 i figured it out... At the start go for nodejs like it would be little easy to understand the concepts of backend after that with time you can switch to .net if you want to... I'm working with nodejs right now 😊
Node ecosystem is garbage in my opinion. 4 years experience in js/ts and I have learnt multitude new orms, frameworks and other stuff that in c# got one solution that everyone use and that is first party supported. I started with c# just 3 weeks ago, transition was very easy. I will stay with it for a while. I want to finally learn patterns, better programing solutions and not damn orm or framework or validation library or other crap every project or two.
@@sebastiandrozd233 best wishes to you brother... I hope in the near future I'll switch but just for now I'm in node 😊
why not just use :name for the node one? That would be a lot simpler...
Not apples to apples comparison considering
In GET, dotnet is sending plain html while node is sending json
In POST, dotnet uses search params while node uses request body for sending data
and what is that means?
Brother which is best to choose as a backend carrier node js or .net
Node.js and c# classmates, copy homework from me but change a bit to do not be obvious copied. :)
Var? diference types is low performance.