Generics Can Make Your Go Code Slower
tl;dr: "This blog post does not take sides in that debate, or advise where and when to use Generics in Go. Instead, this blog post is about the third side of the generics conundrum: It’s about systems engineers who are not excited about generics per se, but about monomorphization and its performance implications."
featured in #304
An Introduction To Generics
Ian Lance Taylor
tl;dr: Generics adds 3 new things to Go: (1) Type parameters for function and types. (2) Defining interface types as sets of types, including types that don’t have methods. (3) Type inference, which permits omitting type arguments in many cases when calling a function.
featured in #302
Three Minor Features In Go 1.18
tl;dr: (1) Version control information included in the binary. (2) New http.MaxBytesHandler middleware (3) Unreasonably effective strings.Cut function.
featured in #279
Trying Out Generics In Go
tl;dr: "I think that generics will be very beneficial to maintainers who create libraries for things like... searching, sorting, transformations, and the like. I can also see some them being extremely helpful for creating well-tested libraries around the various concurrency patterns that are sometimes tricky to get right."
featured in #278
Which Go Router Should I Use?
tl;dr: "There are probably more than 100 different routers available, all with different APIs, features, and behaviors." Alex evaluates 30 popular ones with a shortlist of the best options with a flowchart to help guide you.
featured in #259
Go'ing Insane: Endless Error Handling
tl;dr: "My goal is not to convince you that Go is an objectively bad language, it’s to convince you that for certain people, working in Go feels like a constant struggle against stupid constraints."
featured in #254
A New Way Of Blogging About Golang
featured in #248