Coming to Go from C#: What I had to unlearn — Code nomad

Generated by Gemini

Introduction

I have been a backend developer for the past 30 or so years, and the last 20 years I spent most of my time writing in C#, mostly for ASP.NET applications. And although I love C# ,a couple of years ago I stumbled upon a language called Go. This language seemed easy to learn and fast. The opinions expressed in the article are entirely my own

The Good

Let’s start with the fact that Go seems simple, on the surface, especially when compared to a language like Rust. This is not say that Rust is bad, I like Rust, and like Go it has its strengths and weaknesses.

With Go I could whip up a simple Web application in minutes. With a little more work I could add more endpoints and a database, all working superfast. You have a choice which API framework to use, either the one provided in the Go standard library, Chi, GIN, Fiber and many others. The same went for the database framework. Those who have read my previous posts know that I am not too big a fan of ORMs, but even if you want an ORM there is GORM for example.

When developing in C# you are used to importing nuget packages to write for example an ASP.NET Web API. This is not a bad thing, but having basic things like http serving and routing in the standard library is quite a…