The Case for C# and .NET

The Dependency Problem

The Security Problem

The Performance Problem

The Productivity Problem

OK, So Server-Side JavaScript Sucks? Why Is It EVERYWHERE?

So Why/Not .NET?

--

--

--

I Make Software ▪ Currently obsessed with C#, .NET 6, TypeScript, Vue.js, NoSQL, and serverless!

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Using BestChange: as easy as pie

Pragmatic approach to software architecture decisions

The “Clash of Styles” Series — FP vs. OOP as a Daily Choice

Technical Framework Foundations

K8s Services & Ingress Controllers

Salesforce and Quickbooks Online Integration Using DBSync

“If it turns out that this is incurable, would you marry me?”

Mediator Design Pattern In .NET C#

The Mediator Design Pattern in DotNet (.NET) CSharp (C#) with code samples Mediatr Software Architecture Engineering Development Coding Programming Best Practice Enhancement

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Charles Chen

Charles Chen

I Make Software ▪ Currently obsessed with C#, .NET 6, TypeScript, Vue.js, NoSQL, and serverless!

More from Medium

Add ServiceNow to .NET Apps with Data Connectors & ADO.NET

.NET 6 Web APIs with OpenAPI TypeScript Client Generation

Creating a Cust JsonNamingPolicy

Server-side rendering in ASP.NET Core Angular (2022 version)