I’m pretty new to it. The types and struct stuff are a bit hand-wavey, but I like how quickly I was able to ramp into it. I built a simple API with it in a few hours.
2 things I like about golang is just 1) the ease of getting someone to start work, and 2) goroutines. I have no complains about goroutines cause I’ve barely used it, and when I do it’s been fine. The first point though, I’d say the simplicity of the language is a double-edged sword — it’s easy to learn with little surface to cover, but it forces you to implement a lot of basic machinery you find in other languages by yourself, and so your codebase can get clunky to read really quickly, especially as your project grows.
Not trying to dissuade you from learning golang tho. I think it’s a good language to learn and use, especially for small simple programs, but it’s not the great language many try to say it is. It’s… fine. There are many reasons why it grinds my gears, but I’m still fine with using it and maintaining it for prod.
“Clunky” - this hit it on the head for me. When I was initially getting started, some of the setup and boilerplate felt awkward. It feels very barebones, which I can see the benefit if you’re not a fan of opinionated, but as a project grows, it seems like a dark corner that technical debt and spaghetti code would amass.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
I’m pretty new to it. The types and struct stuff are a bit hand-wavey, but I like how quickly I was able to ramp into it. I built a simple API with it in a few hours.
2 things I like about golang is just 1) the ease of getting someone to start work, and 2) goroutines. I have no complains about goroutines cause I’ve barely used it, and when I do it’s been fine. The first point though, I’d say the simplicity of the language is a double-edged sword — it’s easy to learn with little surface to cover, but it forces you to implement a lot of basic machinery you find in other languages by yourself, and so your codebase can get clunky to read really quickly, especially as your project grows.
Not trying to dissuade you from learning golang tho. I think it’s a good language to learn and use, especially for small simple programs, but it’s not the great language many try to say it is. It’s… fine. There are many reasons why it grinds my gears, but I’m still fine with using it and maintaining it for prod.
“Clunky” - this hit it on the head for me. When I was initially getting started, some of the setup and boilerplate felt awkward. It feels very barebones, which I can see the benefit if you’re not a fan of opinionated, but as a project grows, it seems like a dark corner that technical debt and spaghetti code would amass.