A Love Letter to .NET

Matt Eland on September 24, 2019

With Microsoft's official release of .NET Core 3 today, I want to give you my perspective on .NET and tell you how the platform continues to innova... [Read Full]
markdown guide
 

I have been using .NET on and off for almost a decade now and I hate the fact that it is being stigmatized in the dev community (less so now than before though).

Blazor is one of the things that I am very excited about!

 

Did you have the tall flip-out cardboard version, with (I think) 6 CD's and a DVD of the .NET Beta? I can still recall writing my own site in that, setting up XSLT transforms with some basic AJAX script (All the buzz words at the time)... Brings back memories :D

 

I was a student programmer at University of Wisconsin at the time, working on a fitness center web app for them, so I never saw a box, but back in the day, massive boxes like that were common.

 

Great post.

I have been using .NET for about 6 years now and have loved it. It got a bad name for a while from developers, still does sometimes, but most of them never really sat down to try .NET Core.

Blazor is very interesting and it's very fun to play around with. I wouldn't build a production web app on it just yet, but I'm really excited to watch how it grows. I'm big into Web Assembly being part of the future.

 

With .NET Core, developers can now integrate AI and ML capabilities into their apps with ease. The ecosystem is getting better and broader, and many other big companies such as Google, Amazon, Samsung etc. are betting on .NET. What a time to be a .NET developer.

 

I've been using .NET since around the same time! Even though full-time I focus on full-stack JavaScript/TypeScript, I run a website built on .NET. Now the issue is I am migrating to .NET Core so that I can run on Linux which will save me on cost but also I've become a pretty big fan of the JAMStack architecture so ideally I'd like to remove the MVC tier and switch to only an API and perhaps use Next.js for the frontend (which allows me to scale to SSR in the future if needed).

After using TypeScript so much now though, I find myself wanting a lot of the type features in C#. I know I could use F# but to be honest it can be really hard to interop with C# libraries. F# is good as a consuming language in an app but less-so as a library language.

 

Thanks for this post, I started to look at .Net core recently and found it really enjoyable, love signalR. As a front-end I'm really looking forward playing with Blazor!

code of conduct - report abuse