Tag go

 Like

Liked Why Go is my favorite programming language by Michael Stapelberg 
Post details
I strive to respect everybody’s personal preferences, so I usually steer clear of debates about which is the best programming language, text editor or operating system. However, recently I was asked a couple of times why I like and use a lot of Go, so here is a coherent article to fill in the blanks of my ad-hoc in-person ramblings :-).

 Like

Liked Chris Siebenmann (@cks@mastodon.social)
Post details
Today, if you publish a popular Go module on a URL and you lose control of the URL (through, eg, domain expiration and having the domain snatched up), you have a problem that's probably more or less impossible to deal with short of making blog/Fediverse/etc posts about the situation. Go module identity is tied to URLs with more or less no external override or way to automatically announce and see problems (individual people can override for their usage, but that doesn't scale).

 Like

Liked Talk Notes: Advanced JSON Handling in Go by Jonathan Hall 
Post details
For more content like this, buy my in-progress eBook, Data Serialization in Go⁠, and get updates immediately as they are added! This post contains links and notes for the presentation I gave on March 5, 2020, for the Golang Rotterdam meetup group. Download the slides in PDF format, or you can view the Go Present source file. Previous blog posts on related topics: “Slightly” custom marshaling JSON Arrays as Go structs

 Like

Liked RIP AWS Go Lambda Runtime | Mark Wolfe's Blog by Mark Wolfe 
Post details
Amazon Web Services (AWS) is deprecating the go1.x runtime on Lambda, this is currently scheduled for December 31, 2023. Customers need to migrate their Go based lambda functions to the al2.provided runtime, which uses Amazon Linux 2 as the execution environment. I think this is a bad thing for a couple of reasons: There is no automated migration path from existing Go Lambda functions to the new custom runtime. Customers will need to manually refactor and migrate each function to this new runtime, which this is time-consuming and error-prone.

 Like

Liked Ergonomic Map in Go
Post details
In many languages, on of the things I find myself doing is maping over a list to extract some field. For example, coverting a []Person to []Name. Most languages these days have ways to do this pretty easily: Kotlin: people.map { it.Name } JavaScript: people.map(p => p.Name) Rust: people.map(|p| p.Name) Scala: people.map(_.Name) With generics, Go finally can do this in a type safe manner: Map(people, func(t Person) string { return t.