When is .NET more performant than Go?
.NET Core vs. Golang server costs?
How does Golang compare to ASP.NET Core 6.0 + EF Core 6.0 for backend web development?
Equivalent for ASP.NET Core?
Which framework, .NET Core or Go, is better for building high-performance applications?
Can I achieve comparable performance with both .NET Core and Go?
Can I use both .NET Core and Go together in a single application?
Videos
I often hear that Golang is such a fast language that server costs strive for zero. I was especially stunned when saw Ben Davis's GoLang Review video, where he stated that server costs for his new startup with 'tens of thousands users' (source: https://youtu.be/kUoPdQwyABA?si=d8aCXjTOY4B42uEi&t=204) VIDEO LINK WITH TIMESTAMP WHERE HE SHOWS HIS CLOUD PROVIDER DASHBOARD, NOT PROMOTING ANYONE barely exceed 3 dollars. I did really like that because I am planning on building an app to try my skills and I would very appreciate it if server costs would not exceed a couple of dollars. That sounds like a miracle, but I guess that's why Golang is so popular.
So, my question for the .NET community is - how much worse would be my server billing if I choose .NET Core? I am planning on building an application using htmx + razor pages as a template engine, just because I found it interesting to play with htmx and I do not know javascript and do not really want to. In Golang that would probably be core html/template package?
Keep in mind please that I am living in one of the poorest countries in Europe and even a couple of dollars matter, especially when your project is non-profit.
I've been learning C# 10 and the .NET 6 ecosystem, however I feel that despite the large effort to minimize the "framework", an application made with pure .NET BCL (even without ASP.NET Core) is somewhat bloated, slow and hard to configure. C#10 has a lot of new modern features for coding yet still preserve old features from 5 years ago for the sake of backwards compatibility, resulting in a somewhat bloated language that has 10 ways of doing the same thing without being clear which one is the most optimal way.
This is my first impression after learning C# 10 and the .NET 6 BCL for a week, I haven't even gotten to ASP.NET Core yet, but with what I am learning now, I have a feeling that learning this humungous platform will take me years to have enough experience and knowledge for an entry level job as a backend .NET engineer.
Looking at jobs in my local area, Golang seems to also be used a lot for backend development. But it lacks the maturity that ASP.NET Core 6.0 has, the "framework" has a lot of integrated features that are coherent with one another and reduces a lot of the headache that comes with developing backend compared to other frameworks like Node.js. That's the general consensus I got from the community.
What are your thoughts on it? How does ASP.NET Core 6.0 compare to Golang for backend framework? Does Golang have an ORM like .NET has for Entity Framework? I'm absolutely frustrated by the convoluted monster that is .NET, but not sure if I should drop everything that I've learned so far and switch to a completely new language or if I should stick with .NET because I have already been learning it for some time.
EDIT: I should clarify in this post context, I'm not just referring to "GoLang", but rather the GoLang's ecosystem and popular backend framework used in Go. It's not clear to me which backend framework is used in Go, the community seems to be split on this. But on the C# side, there's really only one framework for backend development (ASP.NET Core). It's more easier to refer to ASP.NET Core specifically than it is to refer to C#.
I'm new to go.
I've been through the tutorials and am comfortable with the language so far. I now want to write a web app (backend api).
But I think using go by itself will be difficult and probably a waste of time.
I typically use C# and ASP.NET Core - in which case there is a difference between the language (c#) and the web framework (asp.net core). ASP.NET does an incredible amount of stuff - config, ioc/di, auth, routing, validation, db work using an ORM, server-side rendering (if you want it), etc.
Is there an ASP.NET Core equivalent in the go world?
I found dozens of options, but can't tell which is the most stable and heavily used by the go community.