aboutsummaryrefslogtreecommitdiff
path: root/content/blogs/technology
diff options
context:
space:
mode:
authorFuwn <[email protected]>2024-06-23 19:17:52 -0700
committerFuwn <[email protected]>2024-06-23 19:17:52 -0700
commit1ad2d662b0f62b7593b6bd623e32eadb0339ce09 (patch)
tree941e5882c3825d5d9d946c85731666db557a174f /content/blogs/technology
parentfeat(footer): add gopherhole link (diff)
downloadlocus-1ad2d662b0f62b7593b6bd623e32eadb0339ce09.tar.xz
locus-1ad2d662b0f62b7593b6bd623e32eadb0339ce09.zip
refactor(blogs): shift content
Diffstat (limited to 'content/blogs/technology')
-rw-r--r--content/blogs/technology/Forth.gmi10
-rw-r--r--content/blogs/technology/Go.gmi50
-rw-r--r--content/blogs/technology/OCaml.gmi4
-rw-r--r--content/blogs/technology/Rust.gmi3
-rw-r--r--content/blogs/technology/blog.json25
5 files changed, 92 insertions, 0 deletions
diff --git a/content/blogs/technology/Forth.gmi b/content/blogs/technology/Forth.gmi
new file mode 100644
index 0000000..788b5dc
--- /dev/null
+++ b/content/blogs/technology/Forth.gmi
@@ -0,0 +1,10 @@
+## Resources
+
+=> http://www.forth.org/ Forth Interest Group Home Page
+=> https://forth-standard.org/ Forth
+=> http://theforth.net/ the Forth Net
+=> http://www.complang.tuwien.ac.at/forth/program-links.html Links to Forth Programs
+=> https://github.com/uho/docker-forth Docker images for popular Forth systems
+=> http://forthworks.com/ ForthWorks (HTTP)
+=> gemini://forthworks.com/ ForthWorks (Gemini)
+=> gopher://forthworks.com:70/ ForthWorks (Gopher) \ No newline at end of file
diff --git a/content/blogs/technology/Go.gmi b/content/blogs/technology/Go.gmi
new file mode 100644
index 0000000..ed584b4
--- /dev/null
+++ b/content/blogs/technology/Go.gmi
@@ -0,0 +1,50 @@
+=> https://www.ardanlabs.com/images/gopher-kart/other-gophers.png
+
+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**.
+
+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. :=
+
+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.
+
+> [0] Having the aforementioned quality is not particularly a bad thing, I think it actually benefits Go!
+
+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: 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: 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 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 ...
+
+* 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!
+
+## 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
+=> https://go.dev/wiki/Plan9 Go Wiki: Go on Plan 9
+=> https://9lab.org/plan9/go/ Plan9/Go
diff --git a/content/blogs/technology/OCaml.gmi b/content/blogs/technology/OCaml.gmi
new file mode 100644
index 0000000..15c6ce7
--- /dev/null
+++ b/content/blogs/technology/OCaml.gmi
@@ -0,0 +1,4 @@
+## Resources
+
+=> https://www2.lib.uchicago.edu/keith/ocaml-class/why.html OCaml for the Skeptical
+=> https://softwareengineering.stackexchange.com/questions/62685/why-isnt-ocaml-more-popular Why isn't OCaml more popular? \ No newline at end of file
diff --git a/content/blogs/technology/Rust.gmi b/content/blogs/technology/Rust.gmi
new file mode 100644
index 0000000..32b798f
--- /dev/null
+++ b/content/blogs/technology/Rust.gmi
@@ -0,0 +1,3 @@
+## Resources
+
+=> https://ceronman.com/2021/07/22/my-experience-crafting-an-interpreter-with-rust/ My experience crafting an interpreter with Rust \ No newline at end of file
diff --git a/content/blogs/technology/blog.json b/content/blogs/technology/blog.json
new file mode 100644
index 0000000..efbfcfe
--- /dev/null
+++ b/content/blogs/technology/blog.json
@@ -0,0 +1,25 @@
+{
+ "description": "Thoughts and Resources of the Programming Languages and Technologies I Actively Use and Have Used",
+ "posts": {
+ "Go": {
+ "author": "Fuwn",
+ "created": "2021. 07. 19.",
+ "last_modified": "2024. 06. 17."
+ },
+ "Forth": {
+ "author": "Fuwn",
+ "created": "2022. 04. 21.",
+ "last_modified": "2022. 04. 21."
+ },
+ "OCaml": {
+ "author": "Fuwn",
+ "created": "2021. 07. 23.",
+ "last_modified": "2021. 07. 23."
+ },
+ "Rust": {
+ "author": "Fuwn",
+ "created": "2021. 07. 23.",
+ "last_modified": "2021. 07. 23."
+ }
+ }
+}