aboutsummaryrefslogtreecommitdiff
path: root/content
diff options
context:
space:
mode:
authorFuwn <[email protected]>2024-06-17 06:25:06 -0700
committerFuwn <[email protected]>2024-06-17 06:25:06 -0700
commitb28fd20b90c5f29fc624d99a658b604867ad7842 (patch)
tree1a44812e85cb6d0f84d889e85b29f7444f4ddbbd /content
parentblog: create The Daily blog (diff)
downloadlocus-b28fd20b90c5f29fc624d99a658b604867ad7842.tar.xz
locus-b28fd20b90c5f29fc624d99a658b604867ad7842.zip
blog(programming_languages): update go
Diffstat (limited to 'content')
-rw-r--r--content/blogs/programming_languages/Go.gmi45
-rw-r--r--content/blogs/programming_languages/blog.json2
2 files changed, 25 insertions, 22 deletions
diff --git a/content/blogs/programming_languages/Go.gmi b/content/blogs/programming_languages/Go.gmi
index 1f2e8b2..ed584b4 100644
--- a/content/blogs/programming_languages/Go.gmi
+++ b/content/blogs/programming_languages/Go.gmi
@@ -1,47 +1,50 @@
-Golang... Go is quite a funny language to me. I have a hard time taking it seriously, not because of the name, but because of the way it handles. Don't get me wrong, Go is a great tool to have under your belt, but it just feels very... "childish" ... to ME.
+=> https://www.ardanlabs.com/images/gopher-kart/other-gophers.png
-Other than the weird chills I get whilst working with it (I just had to get that off my back, for the record), I think Go is a pretty nifty language. Go has the "I can do anything! just not very well..." [0] feeling to it, and it is very much true! I don't write software in Go because it "fast!" or "great on memory!", I write software in Go because it "fast! ...", "to write in!".
+To kick it off: Go is funny language. I have a hard time taking it seriously, and that's not because of the name, but because of the way it "feels". Don't get me wrong, Go is a **great** tool to have under your belt, but it just feels very ... "childish" ... to **me**.
-> [0] Having the aforementioned quality to it is not particularly a bad thing, I think it actually benefits Go!
+Other than the chills I get whilst working with it, I think Go is a pretty nifty language, and I'm sure you'll pick up on that further down in this blog post. If anything, the above statements were icebreakers, but also my genuine feelings. :=
-Now, allow me to list some pros and cons that I have to say about Golang with some things to note while reading:
+Go has the "I can do anything! just not very well ..." [0] feeling to it, and that is very much true! I don't write software in Go because it's "blazing fast!" or "great on memory!". I write software in Go because it's "fast!" to write in.
-These are ...
+> [0] Having the aforementioned quality is not particularly a bad thing, I think it actually benefits Go!
-* in no particular order
-* my opinions!
-* things that aren't explicitly advertised
+Now, here are some pros and cons that I have gathered up during my experience with the language:
+
+These are in no particular order, and solely **my** opinions.
## Pros
Reasons for anyone to learn or to use Go!
-* Fast enough: Not Rust fast, but not Python slow
-* Lots of resources (books, documentation, libraries, tutorials, et cetera)
-* Quite easy to pick up (having had prior experience with C-like programming languages)
-* Can do just about anything!
+* Fast enough: Go isn't Rust fast, but it's not Node.js slow.
+* There are **lots** of resources. (books, documentation, libraries, tutorials, et cetera)
+* It's quite easy to pick up. (having had prior experience with C-like programming languages)
+* Go can do just about anything you pin at it.
+* It runs on Plan 9!
## Cons
Nitpicks, not deal-breakers!
-* Garbage collected: Not necessarily a hard-con, but contributes to more memory overhead (not as much as Node.js though)
-* Can be too simple at times
-* Creepy dependency management and "package manager": `$ go get ...` seems pre-mature and underdeveloped
+* Garbage collected: This isn't necessarily a hard-con, but it contributes to more memory overhead that I'd prefer not to waste. (not as much as Node.js, though)
+* Go can feel *too* simple stupid at times, and not in a KISS way.
+* The dependency management and "package manager" is downright creepy: `$ go get ...` seems extremely pre-mature and underdeveloped, even many years into Go's life
-One thing you might see a lot when there is talk about Go is the claim that Go hasn't "found it's niche" or "it has no real purpose". To that I say; Go's niche is it's simplicity, it's ability to introduce someone into the compiled language space, and to develop software with speed.
+One thing you might see a lot when there is talk about Go is the claim that Go hasn't "found it's niche" or "it has no real purpose". To that I say: Go's niche is its simplicity, its ability to introduce someone into the compiled language space, and to develop software with speed.
## Who Would I Recommend Go To?
-People who...
+People who ...
-* don't have much time for boilerplate material
-* want to get into programming (or compiled languages)
+* don't have much time for boilerplate material,
+* people who want to get their foot into the lower-level side of programming, (or compiled languages)
-and dare I say it... anyone!
+and dare I say it ... anyone!
## Resources
=> https://golang.org/ golang.org
=> https://interpreterbook.com/ Writing An Interpreter In Go by Thorsten Ball
-=> https://compilerbook.com/ Writing A Compiler In Go by Thorsten Ball \ No newline at end of file
+=> https://compilerbook.com/ Writing A Compiler In Go by Thorsten Ball
+=> https://go.dev/wiki/Plan9 Go Wiki: Go on Plan 9
+=> https://9lab.org/plan9/go/ Plan9/Go
diff --git a/content/blogs/programming_languages/blog.json b/content/blogs/programming_languages/blog.json
index a35f9f4..bfb1f52 100644
--- a/content/blogs/programming_languages/blog.json
+++ b/content/blogs/programming_languages/blog.json
@@ -4,7 +4,7 @@
"Go": {
"author": "Fuwn",
"created": "2021. 07. 19.",
- "last_modified": "2021. 07. 20."
+ "last_modified": "2024. 06. 17."
},
"Forth": {
"author": "Fuwn",