/Go

Eleven Years Of Go

- Russ Cox tl;dr: Milestones the team have achieved, including the improvement of gopls, which enables advanced Go-aware support in many editors, and more.

featured in #215


Announcing The 2020 Go Developer Survey

- Alice Merrick tl;dr: "The specific questions each person will see are randomly selected, so folks who’ve taken the survey in prior years may not see all of the questions they are used to."

featured in #212


Even In Go, Concurrency Is Still Not Easy (With An Example)

- Chris Siebenmann 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

- Rob Pike 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

- Chris Siebenmann 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 1.15 Is Released

tl;dr: Substantial improvements to the Go linker, improved allocation for small objects at high core counts, and more.

featured in #200


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!

- Jon Bodner 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


Lisp 1.5

tl;dr: "It is a pedagogical experiment to see just how well the interpreter (actually EVALQUOTE/ APPLY) defined on page 13 of that book really works."

featured in #187


The Next Step for Generics

- Ian Lance Taylor Robert Griesemer 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