this post was submitted on 13 Sep 2024
60 points (86.6% liked)
Programming
17091 readers
194 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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That’s only true in crappy languages that have no concept of async workflows, monads, effects systems, etc.
Sad to see that an intentionally weak/limited language like Go is now the counterargument for good modeling of errors.
I naively thought it I may as well take a job using Go, as learning a new language is broadening, and some people like it, so lets find out first hand... I knew it was a questionable choice, looking at how Go adoption tailed off a while ago.
Turns out I hate Go. Sure it's better than C but that's a very low bar, and C was never a good alternative choice for the use cases I'm encountering. I'm probably suffering from a codebase of bad Go, but holy shit it's painful. So much silent propagation of errors up the stack so you never know where the origin of the error was. So very much boilerplate to expand simple activities into long unreadable functions. Various Go problems I've hit can be ameliorated if you "don't do it like that", but in the real world people "do it like that" all the time.
I'm really starting to feel like there are a lot of people in the company I've joined who like to keep their world obtuse and convoluted for job security.