This is a cool tip I picked up from checking out other peoples' Go projects.
When you're new to Go, the documentation tells you about $GOPATH
which tells Go where to install packages and where the source codes to your project and its dependencies live. A lot of people might set $GOPATH
to be $HOME/go
, and work on their projects out of ~/go/src/github.com/myname/myproject
.
This is something I wanted to rant about for a while: event loops in programming.
This post is specifically talking about programming languages that don't have their own built-in async model, and instead left it up to the community to create their own event loop modules instead. And how most of those modules don't get along well with the others.
Over the last couple months I've been slowly working on rewriting RiveScript in yet another programming language: Google's Go language! It's also my first project in Go, which is what tends to be the case (rewriting RiveScript in Java and Python were my first projects in those languages, too).
But this is the last time I'm going to be rewriting RiveScript from scratch.
0.0016s
.