What do you think about the future of ASP.NET Core or .NET Core in general?

[kaeltran16]

No description provided.

[coryhouse]

I tried it early on. I was too early because it was very frustrating to get started due to constant API churn and a lack of solid tooling. I haven't tried it lately since I'm fixated JavaScript and Node these days.

I've come to prefer Node for APIs over .NET so I can work in JS on the client and the server. This means I don't have to context switch between client and server code. I can share tooling, editors, build processes, bundlers, and so on between client and server solutions. I don't have to keep up with multiple languages, ecosystem, IDEs, etc. Shoot, keeping up with JS, CSS, HTML, and Node is enough as is! :) The Node ecosystem is massive and npm is the largest and fastest growing package manager in history by far. So I have no issues finding what I need in a pure JS ecosystem for UIs and APIs.

That said, I think Core has a bright future given all the existing C# and .NET dev out there. And core is faster than Node. So if raw performance is your goal, .NET core and Go are great options today.

[JaphethOlu]

Hi Cory,

Knowing your response to the earlier question. How did you become a Microsoft MVP?

[coryhouse]

Good question. I spoke at a lot of conferences, authored courses, and blogged a lot. Microsoft gives MVPs to people who are active in the community. You need not use Microsoft products. When I first got my MVP, I was coding heavily in C# and .NET and authoring courses on those topics. That's how I got their attention. Since then, I've shifted to mostly JS and Node, but Microsoft has continued to award me MVP status for my contributions in those areas.

Many people assume MVP means you know MS tech best. That's often true, but not always.

And to clarify, I'm still a big fan of C# and .NET, I've just chosen to focus on JS recently because it's hot and I'm having fun trying to keep up with all the churn. :)