You guys really have to understand the advantages and limitations of both runtime before saying Im choosing this or this is better. I see a lot of ignorant comments here saying Node is better and javascript is the best language (... really????) Node is really good as a frontend server that simply pulls data from a datasource without much logic and/or serves server-side rendered html pages (e.g. next.js). As soon as you start having any complicated business logic (i.e. CPU bound tasks), you are screwed because Node is single threaded. This will block the thread and won't be able to serve any request until the logic is executed. Then there is this awful language called Javascript you are forced to use. Good luck working with no types when your code base gets any larger. There is a reason why Typescript is so popular. .Net Core with C# on the other hand is multithreaded so you can write synchronous code and get away with it. In fact if you are not worried about scaling, writing synchronous code might give you more performance. It is a typed language. It is verbose but try writing the same code in Java you would want to kill yourself. .Net Core is under heavy development by Microsoft (having a big company backing is usually a good thing) and has a solid future in my opinion. If you are writing any backend service, .Net Core is a very solid choice
@@tanzimibthesam5861 Whether it be Nest, Express, Fastify, the same limitations of Node apply. As for which Node framework is better, I can't really give you an advice because I haven't used all of them
100% agreed. To me the development experience is a big factor in selecting a framework. C# and .NET Core are very well structured. No mysterious errors, no dependency hell, no typing issues due to JS. If anyone is developing a backend App for a business then .Net Core is miles better than Node.
Speaking as a long-time freelancer... I'm technology neutral. Whatever fits the job, There is no absolute right way to do something but rather a cocktail of factors that are job-specific.. What skills I am most proficient at don't play a factor in what technology I use unless it doesn't matter for the job itself. If the job is big enough and calls for it I'll spend some time earning a new skill rather than try to match my skills to the job. If someone is new to programming this is not practical but as one gains experience, you realize programming is really about design rather than syntax. What matters is understanding what a variable is not so much how each language declares one. Or what's an object. Or what's a lambda expression. etc.. Same story with CRUD. You need some sort of db, you need to work with records, Ditto for security. User-supplied data has to be input and output securely.. Ditto for what's an API, libraries.framework, And so on. the advice I give to any budding developer is learn the basics of at least one very fast statically typed compiled language (C, C++, Rust.. etc).... at least one scripting language (Python, PHP, etc.).. .learn all the main web UI languages (i.e. HTML, CSS, and Javascript).... learn how to do basic CRUD to some relational database, non-SQL database, and REST API for a web app... learn Linux, Bash, and some container technology (e.g. Docker).. .and of course learn internet networking basics (TCP/IP, DNS, HTTP(S), etc) If someone learns these technologies to intermediary level, they can subsequently learn practically anything else to the same level relatively quickly. This doesn't mean you have to be a jack of all trades. You can still specialize but if you decide to specialize you can make a more informed decision of the pros and cons of the technology you've picked to be more proficient in. And even if specialized, it can still be handy to know other ways of doing things when the language you are using is inevitably deficient at some specific task.
My problem with Node and Javascript is the tooling. It seems like every 6 months there is a new framework or library and a new way to do everything. I spend so much time just setting up a dev environment, rather than writing code. .NET is much more consistent, and with Visual Studio you have everything you need to test, debug, and deploy your code.
Same thing with react vs angular. With react you are building the fucking package puzzle. While with angular you can use it right away. Or slap ngrx on top and it will solve 99% of your needs on FE
In my last startup we called those scaling problems "yacht problems". As in, by the time that becomes an issue, we'll be on our yachts somewhere, and it'll be someone else's problem. No yachts so far :)
Apart from cost benefit I don't find much benefit in node, may be because I used to code in .net since beginning of my programming career. So yes, .net core easier to me than node js as it feels more neat to me. No offense Node is excellent but somehow I don't find it that easy.
Prototype-based inheritance is also pretty cool and can be a very powerful feature of JS. But I too really miss LINQ, extension methods, and the great support for multi-threading that .NET / C# has.
If you’re familiar with node it makes sense and you’re not planning to scale the application ( users or developers). Seems like you’re speaking from a side project perspective. You could easily deploy .net core on digital ocean or linode for cheap.
True. It's not as scary as he's making it out to be. They can do the job but if you're comparing then .netcore wipes the floor with nodejs. Nobody said you have to do mobile, web, desktop and games. One of those should do the trick.
The amount of stuff that you will learn on dotnet is almost the same as learning all the new tools that always pops out on node.js and some of those node.js tools doesnt have a good documentation. FOr example fastify when you get stuck of an error you will have a hard time looking for an answer that problem. At least the front end is not that bad. Unlike backend have several kinds of web framework, orms and other libraries that do the same at least on dotnet there is a standard.
I've got my final interview with a well-funded startup tomorrow. Feeling confident and have no idea what to expect but this channel has made software a lot less intimidating over the past few years so I appreciate that.
@@MrKnockout66 I think it went really well. They said I would hear back from them today at the very earliest and that didn't happen but I feel like it went really smooth.
Well, this is interesting because after a couple decades of .Net I was really impressed by how lightweight both Node and Python were in the cloud... but my experience with Python relating to "there's pretty much a library for everything" yes, but they suck.
One of your videos I got recommend was from a couple years back where you said .NET and .NET Core is the way to go - I found it very persuasive and so if your view has changed and of course .NET Core isn’t what it promised to be, maybe pin a comment in those old videos with a link to here?
The thing about choosing frameworks, is that it always depend. It's an alignment of budget, deadline, project and team. I (from a biz pov) like working with a framework that allows me to do more, with less code, and with cheaper workforce/maintenance, at the possible cost of scale/performance (like node), as many have pointed out, by the time scaling becomes a problem, you do have the capacity for major changes/upgrades even full rebuilds...
crikey you opted for dynamically typed JavaScript for the server side? like willingly? good luck buddy, come back in a few years when you realise just how painful dynamical languages are for backend and server side. Like the saying goes "you can build in dynamically typed language, you just can't maintain it". NodeJs is literally one of the worst architecture for server side, because it's basically single threaded event loop, this means any runtime bug can bring down your entire backend, and not to mention that any CPU operation will choke the entire application, while you do have "non blocking connections", those connections are useless as soon as any one of those connections has to do any kind of CPU, because it's single threaded, now you have loads of connections just sitting there blocked on the CPU. There are so many issues with NodeJs, I can not for the life of me see why any software engineer would willingly pick it up for the server side given the excellent other mainstream server side languages that we already have had for ever. In fact the entire premise of NodeJs is flawed "Hey I don't want learn another language" its extremely myopic and dangerous, it's like saying "hey I only know how to use a spoon, I don't want to learn how to operate a chainsaw, so I'm gonna cut down this forest with my spoon"
.net core isn't a child's play. It's so vastly super maintained by specialists from big companies such as Microsoft that one barely has to be afraid of issues with largely scaled apps. With support of Azure, now it's most future proof framework to work with.
I get annoyed by all the different platforms as none of them are perfect. So, I've just stuck with C# because of the tooling. Works really well with my HTMF (similar to HTMX but simplified) front end library. But if I used node then I could reuse some of the code if I was making it work offline too.
Lol I just saw the video to learn c# then look up recent vids and you say node… and this video it looks like you’ve been threatened for you to say c# sucks and learn node
Quite funny, I was just watching your video "Why C# is the Best Language for the Future" And in the middle I decided to check out your content. At this is your newest video. yeaaaa
About the scale about a problem you wanting to have: in enterprise you get a client sign them up and they offer you a scope of operation where you suddenly go from 0 to 100, you need to plan your architecture before hand for this to be handled. Its ok if you are building a SaaS because the user base grows incrementally but if you have a situation where you suddenly get a bunch of users its not a problem you'll want to have because you have 100% of disgruntled users.
I can always related so much to you when you speak about technologies and the trade off of learning one vs. another. As a Data Scientist I love Python in the backend, since I can deploy models and create a rest service relatively easy, but I would love to learn Rust, Go, Scala and get better at making frontends. So much we can learn, we should not get too frustrated by the fact we can not even come close to master 20% of it.
Dotnet has lot of features and its easier to debug while node is like writing code on notepad. Node is light while dotnet is heavy. Node is good for small stuff but dotnet is best for big projects.
Node can handle any kind of project whether small or big. It's a mindset thing. Paypal, Godaddy, LinkedIn etc who moved to it know what they are doing...
@@olumideolaleye1834 be mindful that changing your stack is not likely to be a technical choice. It is likely to be a reaction to the skills market and what languages engineers prefer. We see tech fads come and go with startling frequency.
I would like to get our thoughts on Dart. I am starting to think of moving to dart. It has the same benefit as Node on top of that can compile to a very small footprint. 10mb (for the entire server app /docker container - no additional runtimes required.)
I like when poeple give crap to MS for creating things like Silverlight, WebForms or even Blazor (which is awesome BTW) saying that "it's for poeple who don't want to learn JS", and then say that Node is great, becasue they don't have to learn C# or something else. Yes, one langugage for both front and backend is the dream. Is Node objectively better than .NET? No. Is is good enough though? Welp, in most cases yes. Simple as that :) In the same way as Blazor is good enough to make a normal website. But to be honest, I think that .NET 6 and MAUI will be the game changer. MAUI will be the next Electron. They have a BlazorWebView control that runs Blazor component IN NATIVE PROCESS and "just" renders out th html. You can literally take a web, put in the MAUI container app and just like that it's 100 times faster, and that's neat :)
I agree, but the problem is going to be the open-source ecosystem around Blazor, in the javascript world you can find many free and open-source components. You can find some good third-party components but you have to pay for an annual license and in terms of adoption that does not benefit the framework. The components offered by Microsoft are usually very basic in comparison with third-party vendor components.
@@christian.mar.garcia Agreed, but not every website needs that fancy stuff. Most times all you need is a list, a button, a from with validation and some progress bars, and that's all there. Standard stuff like google maps is already wrapped, so who cares? If you need to push the web tech to the limit, of course go with JS and React or something, but the same applies to backend. If you really want advanced stuff, you won't do Node.js
@@Qrzychu92 On a different node, who cares about websites with lists and buttons? If the required functionality is that simple, there's no point having a debate on "NodeJS vs. .NET" or anything similar at all. It just comes down to preference then. The differences that matter only start to come into play when you need scalable applications with an increasing code base and higher performance requirements.
So you're learning after 10 years that a lot of the design reasons behind things like scaling, etc, are just nerd talk, ego narcissist show off irrelevant baggage. I feel the pain every time a new junior dev joins the team or a mostly academic architect starts overcomplicating things. And it is becoming a bigger and bigger issue as years go by.
I started off learning c# and got my first job using it like you - I switched over to nodejs and react and never looked back. I find c# so verbose now in hindsight and find I need to just Google things way less That being said I'm really glad I started out with c# and feel like it gave me a really good backbone for my programming career
Looks like you had used c# from .net framework era. Currently minimal api, top level statement are allowing you to create web app in same line of code as Express on node.
@@sonicdev599 this is a fair point in my previous job we had to use .net framework. Am sure the experience is vastly improved now with .net 5 especially with vscode
yeah I am an 8 years c# Unity programmager, I started using nodejs recently 4 years ago, and it is so fluid there are so may projects code samples (that works without you having to fight with the api) etc. I am sticking with Nodje because its free style and easy to get up and running.
Scaling is NOT a good problem to have. If you reach a point where you have hundreds of clients with massive user bases and your system is not built to support it, at best it will piss off your clients and cripple you. At worst it will take you down completely.
I have a friend who works with node js, he wastes a ton of time due to the lack of code intellisense, while on dot net I can use a library and know how to deal with it without much read to the documentation, so I can't agree with you
I chose node because of SSR.. I know, you could technically run javascript in a dotnet setup, but even then, you'd be using node with a dotnet wrapper...
After 20 years of .net. I moved to node from .net core as well however, JavaScript has many issues to deal with. I believe Golang is somewhere in between.
I have used both and I will always choose .NET core if I'm doing anything serious. .NET feels very mature and joy to work with. Good luck with the node though. 🙂
Weird. C# is a much nicer language then nodejs - and it has so many nice libraries available for free.. I mean I can see on the front end not using Blazor.. But back end JS? Really?
I still think .net core is better. But I still choose node. Because the only purpose of programming is to build stuff. it's a tool. And learning node is what people are going now so thats fine. Even though we do all azure. There is no scale. I do business problems.
I am also a .NET developer for around 12 years now, i work as a architect in small company around 60 people. Recently i was thinking of trying to migrate to node, for me .NET core and C# are perfect at the moment, but the ecosystem is really locked, Microsoft are only attempting to make it open source they haven't good example is the recent release for .NET Maui, like it works under anything but Linux, of course it's not without it's .NET issues, you have to compile it several different times, you have to have a mac to compile it for mac, in order to do a release you need a certificate etc. For me, it's the inconsistency that drives me mad and i still feel like C# is not that open as open source goes, because they only support the server-side code on operating systems outside windows when it comes to UI it's still the same and the necessity of one language to rule them all is to have a single way of creating beautiful performant user interfaces across all operating systems no one really cares for what sits behind a website or a web system, it's not running windows anyways.. Also, the biggest issue with .NET based systems, is actually security, not sure how many have tried or even wonder how to secure a .NET based web system outside of Azure, but i can tell you it's a real nightmare when it comes down to manage your own security.
I'm not so experienced, but I'm a C# dev and I'm looking to focus on learning NetCore for backend and Angular/React for frontend. I believe in this crossover but is it a reality on the industry? Or most of time will be used Node over NetCore in the backend? (PS: I realize that nowadays NET 7 include also NetCore right?)
Help me pls. I know js well and c# on a beginner level, I know vue staff as well and I wrote some cool stuff with it but as for me backend more interesting thing because you don't need to design fricking components and think about good UI for clients. I'm planning to learn one of this technology as hard as I can for 1 year. What can you advise for me to learn? P.S I'm thinking on js when I need to do some math-algorithmic tasks and Node icon design looks cool
I like node because it is slow, single threaded, i love how 60% of ram is consumed by node. No language or runtime can compete in these areas. Rust, C++,C#,Go all are trash as compared to ultra high performant node js.
There are probably cases when Node is a better choice over .NET, but you don't actually make that case here IMO. It feels like you're describing the .NET ecosystem from 10 years ago. [[.NET Core (last version was 3.1) isn't even the latest version of the .NET product line. .NET 5 came out in late 2020, with .NET 6 (LTS) showing up a year later.]] It's possible (I don't know Node well enough to say) Node is quicker for prototyping, developing MVPs, or easier to learn, and those might be good reasons to pick it over .NET.
gr8 vid like always, can you please mak a crash course on react native and show us how to access the APIs (Camera Gallery Contacts Location...) and how to use React native Navigation pleaseee and tnx a lottt
Chris we support you ALWAYS, ALL of us. With that said, Node is so powerful and scalable and honestly pressure-tested on ALL OS's, boxes. It has an enormous cross-platform design and it is relatively logical to implement.
🔥 If you're learning to code, check out my website 👉 codehawke.com/all_access.html 🔥
Learn more 👉 ruclips.net/video/fpp215OSRV0/видео.html
7 and a half minute video. The perfect length for the attention span of a nodejs developer. Great vid!
Thank you!
You had me at Node :)
Lol Yeah.
Chris- "In business, a problem with scaling is a problem you probably want to have". Best line ever!!!
and usually you ain't gonna need it because your idea never gets that popular
ruclips.net/video/UJqMKL8kM7g/видео.html
imaginary scaling problem
Indeed
Did you see 'I' in title?
lol, the joke about the "execution", you look fine.
I was literally going to say "Is this a hostage video?"
and you were like
"I feel like I'm about to be executed."
😭😭😭🤣😂🤣
You guys really have to understand the advantages and limitations of both runtime before saying Im choosing this or this is better. I see a lot of ignorant comments here saying Node is better and javascript is the best language (... really????)
Node is really good as a frontend server that simply pulls data from a datasource without much logic and/or serves server-side rendered html pages (e.g. next.js). As soon as you start having any complicated business logic (i.e. CPU bound tasks), you are screwed because Node is single threaded. This will block the thread and won't be able to serve any request until the logic is executed. Then there is this awful language called Javascript you are forced to use. Good luck working with no types when your code base gets any larger. There is a reason why Typescript is so popular.
.Net Core with C# on the other hand is multithreaded so you can write synchronous code and get away with it. In fact if you are not worried about scaling, writing synchronous code might give you more performance. It is a typed language. It is verbose but try writing the same code in Java you would want to kill yourself. .Net Core is under heavy development by Microsoft (having a big company backing is usually a good thing) and has a solid future in my opinion. If you are writing any backend service, .Net Core is a very solid choice
Isnt it better to go for nestJs??
@@tanzimibthesam5861 Whether it be Nest, Express, Fastify, the same limitations of Node apply. As for which Node framework is better, I can't really give you an advice because I haven't used all of them
Or just use go lang : D
100% agreed. To me the development experience is a big factor in selecting a framework. C# and .NET Core are very well structured. No mysterious errors, no dependency hell, no typing issues due to JS. If anyone is developing a backend App for a business then .Net Core is miles better than Node.
Go with whatever can do the Job for you properly. Users don't care what tech you use. And you know you can write node with typescript right??
Speaking as a long-time freelancer... I'm technology neutral. Whatever fits the job, There is no absolute right way to do something but rather a cocktail of factors that are job-specific.. What skills I am most proficient at don't play a factor in what technology I use unless it doesn't matter for the job itself. If the job is big enough and calls for it I'll spend some time earning a new skill rather than try to match my skills to the job.
If someone is new to programming this is not practical but as one gains experience, you realize programming is really about design rather than syntax. What matters is understanding what a variable is not so much how each language declares one. Or what's an object. Or what's a lambda expression. etc.. Same story with CRUD. You need some sort of db, you need to work with records, Ditto for security. User-supplied data has to be input and output securely.. Ditto for what's an API, libraries.framework, And so on.
the advice I give to any budding developer is learn the basics of at least one very fast statically typed compiled language (C, C++, Rust.. etc).... at least one scripting language (Python, PHP, etc.).. .learn all the main web UI languages (i.e. HTML, CSS, and Javascript).... learn how to do basic CRUD to some relational database, non-SQL database, and REST API for a web app... learn Linux, Bash, and some container technology (e.g. Docker).. .and of course learn internet networking basics (TCP/IP, DNS, HTTP(S), etc) If someone learns these technologies to intermediary level, they can subsequently learn practically anything else to the same level relatively quickly.
This doesn't mean you have to be a jack of all trades. You can still specialize but if you decide to specialize you can make a more informed decision of the pros and cons of the technology you've picked to be more proficient in. And even if specialized, it can still be handy to know other ways of doing things when the language you are using is inevitably deficient at some specific task.
man i love you vids
getting your perspective on stuff is always super helpful
My problem with Node and Javascript is the tooling. It seems like every 6 months there is a new framework or library and a new way to do everything. I spend so much time just setting up a dev environment, rather than writing code. .NET is much more consistent, and with Visual Studio you have everything you need to test, debug, and deploy your code.
Yep. That being said JavaScript jobs are more common than .net?
@@monsterhunter445 I think that depends on the area you're in, but surely they both are useful skills to have
Same thing with react vs angular. With react you are building the fucking package puzzle. While with angular you can use it right away. Or slap ngrx on top and it will solve 99% of your needs on FE
For me:
Which technology is faster to build? Node
Which technology is more homogeneous? .NET
That's what I went with
Chris, even though you seemed totally serious I thought your comments about your filming location were hilarious!
I could spent 2-3 times of time debugging in Node Over .Net Core. I use net core for serious major project and node for small server and scripting.
In my last startup we called those scaling problems "yacht problems". As in, by the time that becomes an issue, we'll be on our yachts somewhere, and it'll be someone else's problem. No yachts so far :)
That's actually so cool
Waiting for webassembly to take over the world 😀😀
Blazor/Web Assembly is where it is at! Dipped my feet in = "Awesome time, great choice".
Depressed programmer guy
Apart from cost benefit I don't find much benefit in node, may be because I used to code in .net since beginning of my programming career. So yes, .net core easier to me than node js as it feels more neat to me. No offense Node is excellent but somehow I don't find it that easy.
JS is fun, I really like the property bag object approach, but when I use JS, I miss LINQ. A lot.
Prototype-based inheritance is also pretty cool and can be a very powerful feature of JS. But I too really miss LINQ, extension methods, and the great support for multi-threading that .NET / C# has.
@@vinny6935 The cut of your jib, I like it.
If you’re familiar with node it makes sense and you’re not planning to scale the application ( users or developers). Seems like you’re speaking from a side project perspective. You could easily deploy .net core on digital ocean or linode for cheap.
Yeah, I don't think it matters so far
Totally agree, there's so much to learn about .NET Core
True. It's not as scary as he's making it out to be. They can do the job but if you're comparing then .netcore wipes the floor with nodejs.
Nobody said you have to do mobile, web, desktop and games. One of those should do the trick.
The amount of stuff that you will learn on dotnet is almost the same as learning all the new tools that always pops out on node.js and some of those node.js tools doesnt have a good documentation. FOr example fastify when you get stuck of an error you will have a hard time looking for an answer that problem. At least the front end is not that bad. Unlike backend have several kinds of web framework, orms and other libraries that do the same at least on dotnet there is a standard.
I've got my final interview with a well-funded startup tomorrow. Feeling confident and have no idea what to expect but this channel has made software a lot less intimidating over the past few years so I appreciate that.
All the best
How did it go
@@MrKnockout66 I think it went really well. They said I would hear back from them today at the very earliest and that didn't happen but I feel like it went really smooth.
@@bobDotJS great job! I hope you get that call soon
@@bobDotJS did you hear from them?
Well, this is interesting because after a couple decades of .Net I was really impressed by how lightweight both Node and Python were in the cloud... but my experience with Python relating to "there's pretty much a library for everything" yes, but they suck.
Lol
.NET Core has amazing IO performance on Linux (uring) and a great concurrency story. Good luck with node.
True true
Interesting. I am all in with .NET. Jazzed about Blazor WebAssembly too.
do you know how to find a job?
Enjoy debugging a vast enterprise-grade node app because the company hired a bunch of college grad devs to write it because there are 'more if them'.
Small advice, you really would like to edit your videos and add any image to support examples you provide.
One of your videos I got recommend was from a couple years back where you said .NET and .NET Core is the way to go - I found it very persuasive and so if your view has changed and of course .NET Core isn’t what it promised to be, maybe pin a comment in those old videos with a link to here?
You can try nest.js
Nah, it’s still the way to go. As long as Microsoft just slows down with all the new stuff
My problem with Node is JS. The idea is good. The language is horrible.
What is better alternative?
I like to learn baseline worthless stuff. Makes me feel pretensions. I Like it.
this is the most rediculous things i've watched this month lol
Random outdoor walking > execution room
"Why I Chose Node Over .NET Core" - uh, because you you're not a big boi?
The thing about choosing frameworks, is that it always depend. It's an alignment of budget, deadline, project and team.
I (from a biz pov) like working with a framework that allows me to do more, with less code, and with cheaper workforce/maintenance, at the possible cost of scale/performance (like node), as many have pointed out, by the time scaling becomes a problem, you do have the capacity for major changes/upgrades even full rebuilds...
Hello I saw in benchmark tests that .net core is way faster ..also good for both enterprise and startups...??
Your humour is so deadpan, its perfect!
crikey you opted for dynamically typed JavaScript for the server side? like willingly? good luck buddy, come back in a few years when you realise just how painful dynamical languages are for backend and server side. Like the saying goes "you can build in dynamically typed language, you just can't maintain it".
NodeJs is literally one of the worst architecture for server side, because it's basically single threaded event loop, this means any runtime bug can bring down your entire backend, and not to mention that any CPU operation will choke the entire application, while you do have "non blocking connections", those connections are useless as soon as any one of those connections has to do any kind of CPU, because it's single threaded, now you have loads of connections just sitting there blocked on the CPU.
There are so many issues with NodeJs, I can not for the life of me see why any software engineer would willingly pick it up for the server side given the excellent other mainstream server side languages that we already have had for ever.
In fact the entire premise of NodeJs is flawed "Hey I don't want learn another language" its extremely myopic and dangerous, it's like saying "hey I only know how to use a spoon, I don't want to learn how to operate a chainsaw, so I'm gonna cut down this forest with my spoon"
.net core isn't a child's play. It's so vastly super maintained by specialists from big companies such as Microsoft that one barely has to be afraid of issues with largely scaled apps. With support of Azure, now it's most future proof framework to work with.
I get annoyed by all the different platforms as none of them are perfect. So, I've just stuck with C# because of the tooling. Works really well with my HTMF (similar to HTMX but simplified) front end library. But if I used node then I could reuse some of the code if I was making it work offline too.
Lol I just saw the video to learn c# then look up recent vids and you say node… and this video it looks like you’ve been threatened for you to say c# sucks and learn node
Because Gill Bates owns Sicromoft?🤪
Haha he looks like he feels guilty because he didn't chose. NET
Quite funny, I was just watching your video "Why C# is the Best Language for the Future" And in the middle I decided to check out your content. At this is your newest video. yeaaaa
About the scale about a problem you wanting to have: in enterprise you get a client sign them up and they offer you a scope of operation where you suddenly go from 0 to 100, you need to plan your architecture before hand for this to be handled. Its ok if you are building a SaaS because the user base grows incrementally but if you have a situation where you suddenly get a bunch of users its not a problem you'll want to have because you have 100% of disgruntled users.
I can always related so much to you when you speak about technologies and the trade off of learning one vs. another. As a Data Scientist I love Python in the backend, since I can deploy models and create a rest service relatively easy, but I would love to learn Rust, Go, Scala and get better at making frontends. So much we can learn, we should not get too frustrated by the fact we can not even come close to master 20% of it.
ruclips.net/video/UJqMKL8kM7g/видео.html
Learn Django. Then Go.
Your ideas are intriguing to me, and I wish to subscribe to your newsletter
Bring the execution room back
No image processing capabilities? Did you not find nuget ever in those 7 years? lol
Third
Thanks you for taking down your quitting youtube video. Hope you come back.
Dotnet has lot of features and its easier to debug while node is like writing code on notepad. Node is light while dotnet is heavy. Node is good for small stuff but dotnet is best for big projects.
.net core is not heavy. Back end clients with .net 6 are feather light, cross platform _and_ self contained
@@AngusMcIntyre agree. i would agree with original statement a few years ago, but .NET Core has come a long way
Node can handle any kind of project whether small or big. It's a mindset thing. Paypal, Godaddy, LinkedIn etc who moved to it know what they are doing...
@@olumideolaleye1834 be mindful that changing your stack is not likely to be a technical choice. It is likely to be a reaction to the skills market and what languages engineers prefer.
We see tech fads come and go with startling frequency.
I would like to get our thoughts on Dart. I am starting to think of moving to dart. It has the same benefit as Node on top of that can compile to a very small footprint. 10mb (for the entire server app /docker container - no additional runtimes required.)
I like when poeple give crap to MS for creating things like Silverlight, WebForms or even Blazor (which is awesome BTW) saying that "it's for poeple who don't want to learn JS", and then say that Node is great, becasue they don't have to learn C# or something else.
Yes, one langugage for both front and backend is the dream. Is Node objectively better than .NET? No. Is is good enough though? Welp, in most cases yes. Simple as that :) In the same way as Blazor is good enough to make a normal website.
But to be honest, I think that .NET 6 and MAUI will be the game changer. MAUI will be the next Electron. They have a BlazorWebView control that runs Blazor component IN NATIVE PROCESS and "just" renders out th html. You can literally take a web, put in the MAUI container app and just like that it's 100 times faster, and that's neat :)
I agree, but the problem is going to be the open-source ecosystem around Blazor, in the javascript world you can find many free and open-source components. You can find some good third-party components but you have to pay for an annual license and in terms of adoption that does not benefit the framework. The components offered by Microsoft are usually very basic in comparison with third-party vendor components.
@@christian.mar.garcia Agreed, but not every website needs that fancy stuff. Most times all you need is a list, a button, a from with validation and some progress bars, and that's all there. Standard stuff like google maps is already wrapped, so who cares?
If you need to push the web tech to the limit, of course go with JS and React or something, but the same applies to backend. If you really want advanced stuff, you won't do Node.js
Avalonia UI is already the next electron.
@@Qrzychu92 On a different node, who cares about websites with lists and buttons? If the required functionality is that simple, there's no point having a debate on "NodeJS vs. .NET" or anything similar at all. It just comes down to preference then. The differences that matter only start to come into play when you need scalable applications with an increasing code base and higher performance requirements.
So you're learning after 10 years that a lot of the design reasons behind things like scaling, etc, are just nerd talk, ego narcissist show off irrelevant baggage. I feel the pain every time a new junior dev joins the team or a mostly academic architect starts overcomplicating things. And it is becoming a bigger and bigger issue as years go by.
Well! I love your videos as always - simple, concise and trustworthy
Thank you very much!
I just saw a 30 minutes best of Ron Swanson... You definitely have his vibes love it 😅
I started off learning c# and got my first job using it like you - I switched over to nodejs and react and never looked back.
I find c# so verbose now in hindsight and find I need to just Google things way less
That being said I'm really glad I started out with c# and feel like it gave me a really good backbone for my programming career
Honestly JavaScript probably the best programming language.
Do you use Typescript?
You can try nestJS awesome
Looks like you had used c# from .net framework era.
Currently minimal api, top level statement are allowing you to create web app in same line of code as Express on node.
@@sonicdev599 this is a fair point in my previous job we had to use .net framework. Am sure the experience is vastly improved now with .net 5 especially with vscode
yeah I am an 8 years c# Unity programmager, I started using nodejs recently 4 years ago, and it is so fluid there are so may projects code samples (that works without you having to fight with the api) etc. I am sticking with Nodje because its free style and easy to get up and running.
Scaling is NOT a good problem to have. If you reach a point where you have hundreds of clients with massive user bases and your system is not built to support it, at best it will piss off your clients and cripple you. At worst it will take you down completely.
I have a friend who works with node js, he wastes a ton of time due to the lack of code intellisense, while on dot net I can use a library and know how to deal with it without much read to the documentation, so I can't agree with you
Tell him about Typescript
Thats just not true though is it
perhaps he can install vscode
@@caresvlbdjz vscode has nothing to do with code completion or suggestions
nodejs is so bad that people ho uses make a video confesssing theire sims, and begge for forgiveness
Simply put, I prefer to use node. I agree with all of your reasons.
As a web form lover, I agree with the word "awful"😂
Node is not even close to.net core
Really?
Good luck, until you realize that scaling not only applies to size, but to time too.Over time changes become incredibly costly.
New subscriber here. I have to stop watching your vids now because every time I watch one and hear "web forms" I want to die.
I chose node because of SSR.. I know, you could technically run javascript in a dotnet setup, but even then, you'd be using node with a dotnet wrapper...
fourth
Second
Chriss why you delete your videos, they was awesome. :( Plaase upload again and continue with everthing! Big greetings from Serbia! :)
I also wonder where are you at when you recorded it. 😂
But what about PHP?)))
I made the switch years ago
After 20 years of .net. I moved to node from .net core as well however, JavaScript has many issues to deal with. I believe Golang is somewhere in between.
Love your raw videos chris
I have used both and I will always choose .NET core if I'm doing anything serious.
.NET feels very mature and joy to work with.
Good luck with the node though. 🙂
Weird. C# is a much nicer language then nodejs - and it has so many nice libraries available for free.. I mean I can see on the front end not using Blazor.. But back end JS? Really?
Typescript is great for tooling. Also nodejs is an engine, not a language.
node sucks
Lol
If he is using nest.js its just fantastic
I still think .net core is better. But I still choose node. Because the only purpose of programming is to build stuff. it's a tool. And learning node is what people are going now so thats fine.
Even though we do all azure. There is no scale. I do business problems.
Exactly my thoughts.
I am also a .NET developer for around 12 years now, i work as a architect in small company around 60 people. Recently i was thinking of trying to migrate to node, for me .NET core and C# are perfect at the moment, but the ecosystem is really locked, Microsoft are only attempting to make it open source they haven't good example is the recent release for .NET Maui, like it works under anything but Linux, of course it's not without it's .NET issues, you have to compile it several different times, you have to have a mac to compile it for mac, in order to do a release you need a certificate etc.
For me, it's the inconsistency that drives me mad and i still feel like C# is not that open as open source goes, because they only support the server-side code on operating systems outside windows when it comes to UI it's still the same and the necessity of one language to rule them all is to have a single way of creating beautiful performant user interfaces across all operating systems no one really cares for what sits behind a website or a web system, it's not running windows anyways..
Also, the biggest issue with .NET based systems, is actually security, not sure how many have tried or even wonder how to secure a .NET based web system outside of Azure, but i can tell you it's a real nightmare when it comes down to manage your own security.
I think you actually hit the crux here - js developer wanting to write server side code…
.net win Performance and security ,
what you need else !!
Node.js sucks!
They all do
@@realchrishawkes Not .NET Core!
I develop in C# and JavaScript/Node and this argument is just rambling bullshit.
Cuz you have no idea about coding. How dare you to compare a js garbage with the best framework
I'm not so experienced, but I'm a C# dev and I'm looking to focus on learning NetCore for backend and Angular/React for frontend. I believe in this crossover but is it a reality on the industry? Or most of time will be used Node over NetCore in the backend? (PS: I realize that nowadays NET 7 include also NetCore right?)
Can you really bring yourself to use javascript though? 🤢🤢🤮
06:15 hahahaha nice one
Thank you
I chose completely opposite because Node community is very immature even comparing to PHP which is one of the most hated languages
so you suggest javascript for backend instead of .net core? I really need a clear answer pls ?!
Think the titles wrong. It's spelt "My greatest mistake!"
I would like to give a shout-out to all my WebForms devs out 😂
find me a video where he didn't mention Web Forms, ill give you medal...🤣🤣 i don't know what it is and it's too late to ask 🤣🤣🤣🤣
Help me pls. I know js well and c# on a beginner level, I know vue staff as well and I wrote some cool stuff with it but as for me backend more interesting thing because you don't need to design fricking components and think about good UI for clients.
I'm planning to learn one of this technology as hard as I can for 1 year. What can you advise for me to learn?
P.S I'm thinking on js when I need to do some math-algorithmic tasks and Node icon design looks cool
who cares?
my website runs pure html on Geocities. all this chitter chatter is meaningless. i just want to get my warez out to ppl
Lol u must record video in that room. For some reason I find it funny😂
Lol
Before the execution...
.Net Core dev.s
Stand against this wall and make your confession
Tell us why you like node !!
I like node because it is slow, single threaded, i love how 60% of ram is consumed by node. No language or runtime can compete in these areas.
Rust, C++,C#,Go all are trash as compared to ultra high performant node js.
There are probably cases when Node is a better choice over .NET, but you don't actually make that case here IMO. It feels like you're describing the .NET ecosystem from 10 years ago. [[.NET Core (last version was 3.1) isn't even the latest version of the .NET product line. .NET 5 came out in late 2020, with .NET 6 (LTS) showing up a year later.]]
It's possible (I don't know Node well enough to say) Node is quicker for prototyping, developing MVPs, or easier to learn, and those might be good reasons to pick it over .NET.
gr8 vid like always, can you please mak a crash course on react native and show us how to access the APIs (Camera Gallery Contacts Location...) and how to use React native Navigation
pleaseee and tnx a lottt
Single thread vs multithreaded as simple it is.
Chris we support you ALWAYS, ALL of us. With that said, Node is so powerful and scalable and honestly pressure-tested on ALL OS's, boxes. It has an enormous cross-platform design and it is relatively logical to implement.
I like that nuanced qualifier in "relatively logical to write".