Tuesday, September 25, 2018

Should I build my smaller side projects in .NET Core?

I come from a Ruby/Php background initially. I've been thinking of moving towards using the Microsoft tech stack permanently in the future at some point. So at the moment, I'm thinking of building some mini projects in C# to practice with.

However, it is my understanding that C# and .NET Core/Framework are usually built for enterprise level projects. If I wanted to create something simple like a basic blog, do you guys not think that building that in .NET Core is considered overkill? For example, opting to build a simple API in Ruby on Rails would be considered overkill because of its size and immense features and so a smaller library like Sinatra would be considered a better fit for that kind of project.

What do you guys think? Also, can you recommend a way to quickly setup a new project in .NET Core (beside the .NET CLI) to get the ground running on any projects I start, like a boilerplate of some sort. I would ideally want to start my projects in C# as swiftly as possible without too much configuring or overhead.

Should I build my smaller side projects in .NET Core? Click here
  • Blogger Comment
  • Facebook Comment

0 comments:

Post a Comment

The webdev Team