Linus Gasser ineiti

After getting used to GOPATH

When first encountering Golang, usage of GOPATH was really hard: why should everything be in the same directory structure? What about versioning? How can I stop making it break?

Using gopkg.in was a very good band-aid that worked very well for 3 years. Over time we got used to the GOPATH, even when it disappeared into go env GOPATH. We got so used to it, that we started using it in bash scripts, like this:

Keybase proof

I hereby claim:

I am ineiti on github.
I am ineiti (https://keybase.io/ineiti) on keybase.
I have a public key whose fingerprint is 529D 5B27 276D 66AC A362 DE8D D836 2CB7 4719 337E

To claim this, I am signing this object:

	// Returns the link of the richtext link in the given cell. If there
	// is no link, returns an empty string.
	// If there is a link, removes an eventual "mailto:" in front of it.
	// To use it:
	//
	// =getCellEmail(C2)
	function getCellEmail(address) {
	var sheet = SpreadsheetApp.getActiveSheet();
	var formula = SpreadsheetApp.getActiveRange().getFormula();
	var args = formula.match(/=\w+\((.*)\)/i);

	package network

	import (
	"crypto/rand"
	"crypto/rsa"
	"crypto/tls"
	"crypto/x509"
	"crypto/x509/pkix"
	"encoding/pem"
	"errors"


	// All known channels
	var channels map[reflect.Type]interface{}

	// RegisterChannel stores a channel and the message-type
	func RegisterChannel(c interface{}) error {
	if channels == nil {
	channels = make(map[reflect.Type]interface{})
	}
	cr := reflect.TypeOf(c)

	Just to do what https://stackoverflow.com/questions/68777239/how-to-display-an-image-in-readme-file-on-github proposes...