Absolutely. An intermediate path in Go is to recover any panics on your goroutines: in this case a nil dereference panic may cause the death of the goroutine but not the whole application. An example where this can be…
Nice post! To me, "math/big" feels like a big hammer for working on an int64; a nice alternative is "encoding/binary": func atomSlug(publishedAt time.Time) string { b := make([]byte, 0, 8) b =…
The argument laid out in this article is a quite complicated edifice, and requires a large amount of knowledge at the intersection of several fields of study I found this blog post interesting and wish it had a…
Absolutely. An intermediate path in Go is to recover any panics on your goroutines: in this case a nil dereference panic may cause the death of the goroutine but not the whole application. An example where this can be…
Nice post! To me, "math/big" feels like a big hammer for working on an int64; a nice alternative is "encoding/binary": func atomSlug(publishedAt time.Time) string { b := make([]byte, 0, 8) b =…
The argument laid out in this article is a quite complicated edifice, and requires a large amount of knowledge at the intersection of several fields of study I found this blog post interesting and wish it had a…