go podcast(‪)‬ Dominic St-Pierre

I talk about how the internal package can be used wrongly. I recently had to expose a Go package that I never thought would be expose, hence I've heavily used the internal package, a bad decision.

I talk about how I'm using the -LDFLAGS to inject variables value at build time so it's easier to grab the exact Git commit hash that user are using when reporting issues.

I talk about a personal experience where a Go micro-service got csharpify via OOP design pattern and why I think C# / Java developers should approach Go with a much simpler mindset and use Go's design patterns instead of those from the GoF OOP way.

I go over some choices and scenarios Go programmers have regarding options to talk to databases.

I gave 3 reasons why I think Go is one of the best language to build long-live programs. Programs that need to run for 15-20+ years.

Is Generics going to cause a fragmentation in the community? What's the big deal about it, I personally will appreciate less for-loop where it make sense to reduce verbosity.