56
this post was submitted on 15 Jan 2025
56 points (76.9% liked)
Programming
17814 readers
539 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I honestly don't get why people like Go. Structural typing makes it so difficult to find classes that interpret an interface. Every dumb go project has to be opened in an IDE or something with a language server to find implementors of an interface. Also, forcing every capitalised object in a module or struct to be exported is just... wat? Returning a tuple of
whatever, erralso feels wrong. It's like they couldn't decide between throwing exceptions or an enum and went with something in between.I get that the inbuilt concurrency features are nice, but the rest of the language and stdlib feel very lackluster. At least that's my impression after ~2 weeks of it. My retreat to Rust was rather quick.
Anti Commercial-AI license
The stdlib I actually find quite complete. Especially for http projects. You really don't need third party libs for that for example.
The errors were super strange to me at the start, but I've come to really like it over exceptions. It is similar to old error codes, but I feel that this makes one always have to be mindful of error handling and the non happy path (thinking of large Python projects where no one cares about exceptions).
A lot of people tend to compare Go and Rust, but I feel that the languages are just too different. Rust is good for a variety of things which don't overlap with the things Go is good for.
Technically you need a separate linter (
errcheck) to ensure you don't just ignore errors. This is...not great. (That should have been a compiler error.)Yes, true. Having it built in in the compilation would be nice. Or at least having errcheck as a tool which already comes packed with Go.
Go has changed over time to include more things like this. Maybe one day this will be addressed.
Yeah, I was particularly glad to see the change in loop variable semantics become a stable part of the language. That was a terrible footgun.
There are other things I dislike about Go, but I do think it's improving while maintaining its better qualities, which is no small feat.