go
programming
programming language
Written on 2022-04-22 by yours truly
I prefer to call the language go. It's called go. Not golang
DISCLAIMER: I'm a TS dev. Keep that in mind when reading this post.
Like my about page says, I've dabbled in go but mainly worked with TypeScript. I recently picked up go again to do some programming challenges, after I finished a tutorial series and kind of know my way around the language.
Don't get me wrong, I still like TypeScript, but go is absolutely amazing.
Well.
Programming problems, as weird and vague as it may sound. It's quite easy: go is called modern, 21-century C and was designed at Google around 2010 because everyone hated C++.
You can do basically anything in go (as long as it's not writing HTML or CSS or doing anything with websites).
You can do graphics programming with OpenGL, mobile app dev (apparently), but the language is mainly made for the server-side of web development.
Solving small problems to sharpen my problem-solving skills or whatever you want me to say to make me sound interesting.
I've been screwing around, and actually planning to write markdown-thing in go instead of TS. I might throw plans out the window though, but I'd like to devote a full post to that in the near future. I'll explain everything there. Stay tuned :)
Even though TS is way safer than JS, go is like an unlawfully overprotective parent (try to comprehend how bad rust is with safety!!). I like that though.
JavaScript is weird. TypeScript may patch some of it up, but I see JavaScript as broken-beyond-repair.
GitHub-based mirror. Go's tools are really good.
I don't have to explain anything. They're absolutely amazing
Go's standard library consist of some really good packages. And it's documentation is really good.
In summary: my experience with go is really good, and I haven't even barely scratched the surface.
š