From 4cea9c610a074430b9342c4a4f1498cc67c7bf37 Mon Sep 17 00:00:00 2001 From: Wyatt Miller Date: Wed, 13 Feb 2019 16:43:02 -0500 Subject: [PATCH] added paragraph to blog post --- src/blog/_posts/2019-02-15-trying-golang.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/blog/_posts/2019-02-15-trying-golang.markdown b/src/blog/_posts/2019-02-15-trying-golang.markdown index 9f6a372..cdcd2c6 100644 --- a/src/blog/_posts/2019-02-15-trying-golang.markdown +++ b/src/blog/_posts/2019-02-15-trying-golang.markdown @@ -63,4 +63,6 @@ Inside the function, I used the `"fmt"` package to print a line that says "Hello Go has flow control too, which is pretty cool but I haven't messed with a whole lot yet. +The `go` command is really robust too. It has everything to the `run` command which runs your code in go, not compiled (JIT maybe?). It has the `test` command, which runs your tests if you are in TDD mode. It even has the `build` command, which Go compiles your code into binary format. This is were GOOS comes in. As a environment variable, GOOS can target whatever operating system you want to target, which could be very helpful if you are using `build` in a Makefile. + Check Go out, I think you guys will really enjoy it as I am. Next, I might playing with some of [this](https://github.com/zmb3/spotify). \ No newline at end of file