/Chris Siebenmann

Everything That Uses Configuration Files Should Report Where They're Located tl;dr: Chris regularly interacts with various programs, each of which has its configuration files in different locations, sometimes system-wide, other times user-specific. Given the variability and their infrequent interaction with some programs, they struggle to remember the configuration file locations, which can lead to time-consuming searches through manuals or documentation. Their proposed solution is for programs to offer an easy method, preferably via command line, to report the location of their configuration files.

featured in #433

A Realization Of Why Email Is Critical Infrastructure For The Internet tl;dr: "The prospect for another federated, Internet wide communication system seem very remote at this point in time, so email is it." Email is our only reliable communication method between different organizations and, at this point, companies have something to lose if companies try to replace email.

featured in #279

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

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 Is Google's Language, Not Ours tl;dr: Author debates that having a community contribute to GoLang is meaningless as it's owned by Google and, ultimately, the language is controlled by, and designed for, the company's needs.

featured in #142