Even In Go, Concurrency Is Still Not Easy (With An Example)
tl;dr: "Go is famous for making concurrency easy"..."except what Go makes easy is only one level of concurrency." Go doesn't currently provide a lot of standard library support for correctly implemented standard concurrency patterns, highlighted here.
featured in #204
New Case Studies About Google’s Use Of Go
tl;dr: Rob discusses increasingly diverse use cases of Go within Google - in Core Data Solutions, Chrome and Firebase.
featured in #203
How Go 1.15 Improved Converting Small Integer Values To Interfaces
tl;dr: The Go 1.15 release notes mention an intriguing improvement in the runtime section: "converting a small integer value into an interface value no longer causes allocation," discussed here.
featured in #201
Go vs Rust: Writing A CLI Tool
Paulo Henrique Cuchi
tl;dr: Paulo wrote a simple web app in Go and Rust languages, both of which are unfamiliar to him. He evaluates both and concludes with their comparative pros and cons.
featured in #197
Go Is Boring...And That’s Fantastic!
tl;dr: "Studies show that process matters. When properly used, Go’s built-in tooling supports better processes while providing time-tested features." It's what's missing from the language that makes it so.
featured in #191
The Next Step for Generics
Ian Lance Taylor
tl;dr: Go has launched a tool to provide a feel for what generics might look like. Authors want feedback on the implementation - does it make sense? Does it feel like Go? Does it solve the problem for those advocating for generics?
featured in #186
An Intro To Go For Non-Go Developers
tl;dr: A brief overview of the standard library and language features.
featured in #185
The Go Compiler Needs To Be Smarter
tl;dr: Go's compiler is "shy about inlining" and doesn't have a concept of runtime constant variable.
featured in #184