Compared to Go, what areas can .NET not do or do poorly?
When I saw this question, I was momentarily stunned. What areas can Go do that .NET cannot, or that C# cannot?
When I saw this question, I was momentarily stunned. What areas can Go do that .NET cannot, or that C# cannot?
The development of the blog website has gone through many hardships, with nearly 10 versions including MVC, Vue, Go, etc. Now it has returned to Blazor and adopted static SSR, resulting in a significant speed increase and successful launch.
For many developers, this may mean switching to C#, Go, Java, Ruby, Rust and Swift.
Some netizens asked me to share, so I'll briefly talk about it.
One night learning Razor Pages technical points, one day restructuring the website front-end, exhausting!
During the 7 days of National Day, I used my spare time while taking care of the kids to learn Go and made a not very complete blog front-end.
In the past few days, I've been reading a Go book. I've read about 100 pages and it feels good. Sharing it with everyone.
As a backend developer, regardless of the language, Java, Go, or C++, the underlying backend thinking is similar.
It's simple, use it because it's good, performance and syntax expressiveness/development speed are stronger than Java/Go, why not use it.