Hi Dean!
Thank you so much for your answer! It has been insightful and although you were giving your POV from .NET Core rather than .NET 6, the amount of insight you put out is fantastic!
I’ve seen similar complaints in the community when working with .NET Core, but ever since .NET 6 came out, the framework size has reduced significantly and seemed a lot easier to work with as opposed to .NET Core. The current .NET ecosystem aims to be modular and unifies all of the different components and frameworks of .NET Core previously, so that may or may not reduce the amount of clutter you were speaking about.
I’ve already made a decision recently to continue learning .NET 6 and C#10 with the goal to ultimately learn ASP.NET Core 6.0 and its subset, ASP.NET Core 6.0 MVC with React as the frontend view. The main reason being that there are significantly more internship positions in my area for .NET developers than there are for Golang developers. I’m guessing the main reason for this is because Golang is a fairly new language that many businesses have yet to adopt.
I’ve set out a career plan following this pattern, to go from Backend Web Developer → DevOps Engineer (or QA or CI/CD Engineer) → Blockchain Developer (DApps) working with blockchain as my ultimate goal. I definitely plan to learn and work with Golang in the future. But given my situation and the market position of my local area, that’s not the best fit for me right now.