61
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 Jan 2025
61 points (100.0% liked)
Programming
17808 readers
290 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
Yeah, the Go creators seem to generally mean "resembles C" when they use words like "simple", which could explain stuff like going "why do you need generics when you can just cast?" for, what, ten years?
I remember trying some Plan9 stuff and bouncing off it, including acme. I guess it's the kind of thing that makes sense to Pike but not to me. Not sure what gophers in general think of it (but wikipedia lists at least Russ Cox as a user).
And the Garbage Collector in Go is also a thing that helps ton for most normal work. To be honest, I wish sometimes Rust had an optional GC mode (I know this would be against the principles of the language... don't take this wish too seriously). I see it like C with a GC+Concurrency. And one should not forget, because the language is dead simple, the compiler compiles extremely fast; even suitable as an interpreter language basically (purely judging by speed metrics).
But after being exposed to Rust, I do not have fun with Go because it misses some really cool or basic functionality; like proper error handling. Ultimately these are different approaches and that's good. In example functional programming works a bit differently and we are not saying they should give up on this approach, because you like C so much.
Yeah, Rust is ultimately a different project than Go, and I suspect much of the success of Go is down to stuff like good tooling, default GC, native static binaries, generally easy concurrency, rather than stuff like having as bare-bones a language as otherwise possible. I'd suspect having a focus on fast compilation also helps draw in people from interpreted languages.
It's easy to write a Kubernetes microservice that performs adequately with Go, and that's all a lot of people & teams need.