Why I Chose Node Over .NET Core

📣 Other Social:

[PaulPetersVids]

7 and a half minute video. The perfect length for the attention span of a nodejs developer. Great vid!

[azukamojume]

Chris- "In business, a problem with scaling is a problem you probably want to have". Best line ever!!!

[DuraanAli]

lol, the joke about the "execution", you look fine.

[iverson]

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

[shawnradke]

man i love you vids
getting your perspective on stuff is always super helpful

[KeithGraves]

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.

[bobDotJS]

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.

[mydogsbutler]

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.

[splitpierre]

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...

[Tux.Penguin]

Chris, even though you seemed totally serious I thought your comments about your filming location were hilarious!

[stevenlee]

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.

[rileydavidjesus]

I was literally going to say "Is this a hostage video?"

and you were like

"I feel like I'm about to be executed."

😭😭😭🤣😂🤣

[CertifiedMixtapez]

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.

[LorenzoJimenez]

For me:

Which technology is faster to build? Node
Which technology is more homogeneous? .NET

[rosstapson]

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 :)

[AmilJoshy]

Hello I saw in benchmark tests that .net core is way faster ..also good for both enterprise and startups...??

[troymitchel]

I did notice a lot of job postings for nodejs required dotnet C sharp

[TomNook.]

Your humour is so deadpan, its perfect!

[misha]

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.

[mikebreeden]

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.