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

An Intro To Go For Non-Go Developers

- Ben Hoyt tl;dr: A brief overview of the standard library and language features. 

featured in #185

The Go Compiler Needs To Be Smarter

- Daniel Lemire tl;dr: Go's compiler is "shy about inlining" and doesn't have a concept of runtime constant variable.

featured in #184

Go Developer Survey 2019 Results

- Todd Kulesza tl;dr: Go’s usage is concentrated in technology companies with increasing usage in other industries like finance and media. 

featured in #181

Go, The Go Community, And The Pandemic

- Russ Cox Carmen Andoh Steve Francia tl;dr: What the Go community is doing to help with the crisis and how members can get involved. 

featured in #179

A New Go API For Protocol Buffers

- Joe Tsai Damien Neil Herbie Ong tl;dr: We are pleased to announce the release of a major revision of the Go API for protocol buffers, Google's language-neutral data interchange format.

featured in #175

The Zen Of Go

- Dave Cheney tl;dr: 10 values to write simple, maintainable code in Go, starting with each package fulfilling a single purpose and handling errors explicitly.

featured in #173

Why Discord Is Switching From Go To Rust

- Jesse Howarth tl;dr: Switching a service to Rust significantly improved performance. This post outlines how it was done and the improvements. If you are paywalled, click on the link in this tweet.

featured in #172

Star: Go but in Python?

- Max McDonnell tl;dr: "Star is a python(ish) programming environment that lets you call Go library functions."

featured in #172